Project

General

Profile

Actions

Defect #29622

open

Adding a 'Custom Field' to 'Activities (time tracking)' prevents time entry on project change

Added by Ercan Demirel over 5 years ago. Updated over 2 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Time tracking
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:
Affected version:

Description

Two projects have identical values for time tracking activity and custom field:

field_work_settings.png
consulting_settings.png

But if you try to move an issue from one project to the other and create a time entry with that time tracking activity, the following errors occur:

time_entry_error.png

The validation for the time entry should not fail, since both projects have the same activity with the same custom field value.

Our workflow dictates to create a time entry on every issue update, regardless of the content of the update. So moving the issue to another project, then creating a time entry is out of the question.

Seperate values for identical activities can be seen in the database, so inclusion validation always seems to fail:

 19 | QA                      |        3 | f          | TimeEntryActivity | t      |          3 |        14 | 
 18 | QA                      |        3 | f          | TimeEntryActivity | t      |          2 |        14 | 
 14 | QA                      |        3 | f          | TimeEntryActivity | t      |            |           | 


Files

consulting_settings.png (37.9 KB) consulting_settings.png Ercan Demirel, 2018-09-17 10:28
field_work_settings.png (38 KB) field_work_settings.png Ercan Demirel, 2018-09-17 10:28
time_entry_error.png (42.8 KB) time_entry_error.png Ercan Demirel, 2018-09-17 10:28
project-time-tracking-settings.png (89.5 KB) project-time-tracking-settings.png Yuichi HARADA, 2021-12-07 08:54
29622.patch (3.79 KB) 29622.patch Yuichi HARADA, 2021-12-07 09:16
Actions

Also available in: Atom PDF