Making an issue a subtask leads to loss of issue-property values
|Target version:||Candidate for next minor release|
- start/due dates
These changes aren't recorded to issue-journals (besides an entry about the changed parent id), thus are lost without any reminder/notice.
#3 Updated by Chris Wolf about 2 years ago
- File no_priority_rollup.diff added
In my organization, we do want the dates and estimated time to rollup from the subtasks, however, we don't want the priority to rollup - we want the priority set and maintained in the parent task independently of the subtasks. Attached is a hack to implement this. The patch includes the cross-project subtask feature /issues/5487.
This patch is base on release 1.1.2.
#5 Updated by Svein-Tore Griff With almost 2 years ago
Vote for the option where the current solution is kept, but we also keep a separate estimate for the parent task, so that the parent task would have the properties:
Estimated time: 30 hours(editable)
Total estimated time from children: 32 hours
We can do the same for the other properties.
This is side effect issue made on redmine’s trunk
(Affected on Redmine v1.4.0 ~ v2.1.x.)
This patch is workable with my production site: Redmine-v1.4.4
#12 Updated by Bishma Stornelli Ortega 3 months ago
I've just made a patch that works like this:
When an issue is divided in subtasks, the priority, the start/dude date and the estimated time is kept in the parent but additional fields are created to show the calculated values of the subtasks.
The estimated time of an issue must be greater than the estimated time of the subtasks, less than the estimated time of the parent - estimated time of siblings and if the parent has not estimated time, subtasks can't have estimated time.
The done ratio is calculated using the no calculated estimated hours of the issues. Example:
- Issue 1 has 100 estimated hours
- It's divided into Issue 1.1 and Issue 1.2
- Issue 1.1 has an estimated hours of 40 and a done ratio of 50.
- Issue 1.2 has an estimated hours of 30 and a done ratio of 100.
- Then the done ratio of Issue 1 is 40*0.5 + 30*1 = 50.
Dates on subtasks are allowed to be before or after the start/due date of the parent but it's always displayed in the parent issue. Maybe I'll add a validation to avoid this and ensure that all dates in subtasks are between the start and due date of the parent.
This patch was made for version 2.2.1 and there is not warranty it works even in this version because the development was done on an already patched version of redmine and I'm not sure if the files edited were changed previously.
Don't forget to run the migration (it will force update of these attributes for all existing issues).
#19 Updated by Sebastian Bertram about 1 month ago
Unfortunately there was a permission issue, so the log wasn't written. But at the Moment I also think that the Problem maybe only or also comes from the fact, that I am using redmine with German language and the patch only changes the file for the English and Spanish language.
So I think there a two things I can try now. Change the language file and make a migration.
Is there something I have to care about when I add the added lines of the en.ylm to the de.ylm? Other then translation the words after the colon.
Is there a order in which the lines have to be added?