Actions
Defect #28110
closed
Don't allow reassigning reported hours to the project if issue is a required field for time logs
Start date:
Due date:
% Done:
0%
Estimated time:
Resolution:
Fixed
Affected version:
Description
The problem occurs in the latest Redmine version (3.4.2)
Settings:
- Create an issue
- Log time on it
- Delete the issue
The following pops out:
There, we can apply, violating the "required issue" constraint.
Files
Related issues
Updated by Marius BĂLTEANU over 7 years ago
- File do_not_allow_nullify_time_entries_when_issue_is_required_for_time_entries.patch do_not_allow_nullify_time_entries_when_issue_is_required_for_time_entries.patch added
- Status changed from New to Confirmed
- Affected version set to 3.4.4
Stephane, thanks for pointing this out.
Attached is a patch that fixes this issue. Also, it hides the option "Assign reported hours to the project" when the issue is required for time entries.
Updated by Go MAEDA over 7 years ago
- Related to Feature #24577: Settings to make the issue and/or comment fields mandatory for time logs added
Updated by Go MAEDA over 7 years ago
- File do_not_allow_nullify_time_entries_when_issue_is_required_for_time_entries-v2.patch do_not_allow_nullify_time_entries_when_issue_is_required_for_time_entries-v2.patch added
- Target version set to 3.4.5
Marius, thank you for writing the patch. But I slightly modified because the patch cannot be cleanly applied to the current trunk.
I tested the patch and it works fine, setting target version to 3.4.5.
Updated by Go MAEDA over 7 years ago
- Subject changed from Time Entries of an issue pending deletion can be reassigned to the project itself even if issue is a required field to Don't allow reassigning reported hours to the project if issue is a required field for time logs
- Category set to Time tracking
- Status changed from Confirmed to Closed
- Assignee set to Go MAEDA
- Resolution set to Fixed
Committed.
Thank you for reporting and fixing this issue.
Actions