Feature #6687
Making an issue a subtask leads to loss of issue-property values
| Status: | New | Start date: | 2010-10-18 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | Issues | |||
| Target version: | Candidate for next minor release | |||
| Resolution: |
Description
- priority
- start/due dates
- progress
- estimate
These changes aren't recorded to issue-journals (besides an entry about the changed parent id), thus are lost without any reminder/notice.
no_priority_rollup.diff 
- No priority rollup patch.
(2.76 KB)
keep_original_dates_and_estimations_on_parent_issue.diff
(13.5 KB)
de.yml
(50.6 KB)
log redmine.JPG (61.6 KB)
Related issues
History
#1 Updated by Ewan Makepeace over 2 years ago
+1
At least write the values in the history so we can restore the issue as it was if needed.
#2 Updated by Mischa The Evil over 2 years ago
- Priority changed from Normal to High
#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.
#4 Updated by Etienne Massip about 2 years ago
- Target version set to Candidate for next minor release
#5 Updated by Svein-Tore Griff With almost 2 years ago
+1
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.
#6 Updated by Jacq Jacq about 1 year ago
+1
All the properties should be editable and independent from subtasks.
As a option it could be set to get properties from subtasks.
#7 Updated by Radek Karban 12 months ago
+1
#8 Updated by Murray Melvin 6 months ago
I also would like to see something done about this. Svein-Tore Griff With's suggestion would work for me.
#9 Updated by Tim Hsieh 6 months ago
This is side effect issue made on redmine’s trunk
http://www.redmine.org/projects/redmine/repository/revisions/8382/diff/trunk/app/models/issue.rb
(Affected on Redmine v1.4.0 ~ v2.1.x.)
Solution:
http://www.redmine.org/issues/6687
This patch is workable with my production site: Redmine-v1.4.4
Related discussions:
http://www.redmine.org/issues/5490
http://www.redmine.org/issues/5875
http://www.redmine.org/issues/5880
http://www.redmine.org/boards/2/topics/19023
http://www.redmine.org/issues/6847
#10 Updated by Eric Voisard 5 months ago
All these discussions and issues about subtasks just show that this important feature needs serious (and open minded) rethinking.
Or an option to disable subtasks completely...
#11 Updated by Julian S. Luipold 4 months ago
+1
would prefer to have a per project setting for the behaviour of subtasks!
#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).
#13 Updated by Toshi MARUYAMA about 1 month ago
- Tracker changed from Defect to Feature
- Priority changed from High to Normal
#14 Updated by VD DV about 1 month ago
+1
#15 Updated by Sebastian Bertram about 1 month ago
Hi the patch sounds realy good. Did somebody try it? I have a new installed 2.3 version of redmine here and the parent subtask thing is realy annoying
#16 Updated by Sebastian Bertram about 1 month ago
I did try to patch my redmine 2.3 today and I get an internal error when I want to display the issus. I'm glad that I patched with the backup option.
#17 Updated by Sebastian Bertram about 1 month ago
Now I realize that I didn't run the migration. Could the internal error 500 occurred because of that?
#18 Updated by Bishma Stornelli Ortega about 1 month ago
Hello Sebastian, I guess it is. Probably a NoMethodError. You can check the log and print the error message here.
#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?
#20 Updated by Bishma Stornelli Ortega about 1 month ago
No. Just add the lines in any order but make sure you use the right indentation.
#21 Updated by Sebastian Bertram about 1 month ago
- File de.yml added
Ok, now I patched the files again and also changed the de.yml. At the moment I have the problem, that the german translation isn't working for the hole programm. And I don't know why.
Here is the file I created.
#22 Updated by Sebastian Bertram about 1 month ago
- File log redmine.JPG added
And the log shows that. (see file)