Redmine - Feature #13585
Make sub-task inherit the properties of parent
2013-03-25 14:59 - Dipan Mehta

ステータス:

New

開始日:

優先度:

Normal

期日:

担当者:
カテゴリ:

Issues

進捗率:

0%

予定工数:

0.00時間対象バージョン:Resolution:
説明

BackgroundSub-task as such is a pretty much a complete issue like any other. It has it's own values of each custom fields, states, permissions,authors and so on. Currently the only thing common or linked between the parent task and sub-task are dates, closure etc.
However, when we think of sub-task it's not just-another-work-item; else it would be just another relation. Sub-task shouldnecessarily derive it's properties or workflow from parent task - since it is the parent task which defines the 'larger scope' for all its
children.

Some scenarios
1. In many cases - for a given issue, there are many custom fields liek customer-representatives, QA specific attributes, projectand process specific attributes etc. which should be governed by parent issues.
The sub-tasks shouldn't be required to keep copy and updating issues when parent is updated
The sub-tasks sometimes shouldn't be allowed to change some of the properties.
2. Many a times, when we are building a feature, some specific use-cases, exceptions keeps arising. In this case, we create a
sub-task (not a new task). From the customer/accounting point of view it may be regarded as an 'extra work' but from release
or QA point of view the patch for the full parent issue inclusive of all sub-tasks is single. In such cases many feature specificcustom field should be simply 'as per parent'
3. Another example, if the parent feature is 'client approved' the sub-tasks should also get 'client approved'
Currently the shortcut is to 'copy' a task straight away to preserve the values but when the same values change on the parent task the sub tasks should reflect the same.

Approaches
Given this principle, we should be able to define specific behaviors:
1. The target version should get directly linked to sub-task assuming both the sub-task and parent tasks are expected to befinished together.
2. Custom fields of issues can have a properties as 'derive from parent'. Hence they can be automatically linked from parent
tasks.
3. Alternatively, in the "New issue"/"Update" form, the custom fields (even if mandatory) can have option called 'Follow parent'
option which will follow value of parent as applicable. This way, specific properties can be linked to parent without any
standard template.
4. Specific State transition in workflow can have a flag <move sub-task along> which will reflect the corresponding states of theissues as well.
5. Alternatively, when parent's status is changed, additional drop-down of child's status can be selected or can be kept
unchanged if no change is more appropriate.
6. Closure should be completely linked
7. %done of the parent task can be directly derived from the sub-tasks.
There is no assumption that parent task and sub-task are of the same tracker - hence this overlap only applies to states and custom
fields which overlaps in the respective trackers.
What do you people think about it?
関連するチケット:
関連している Redmine - Feature #6217: When creating a subtask, ...

2024-09-08

Closed2010-08-25

1/3

関連している Redmine - Feature #9972: Subtasks assigned to same...

Closed2012-01-10

関連している Redmine - Feature #7057: Send email notification o...

Closed2010-12-06

関連している Redmine - Feature #11177: Email notification for s...

Closed関連している Redmine - Feature #9991: Estate parent task vs sub...

Closed関連している Redmine - Feature #7450: Subtask : automatic statusNew

2011-01-26

関連している Redmine - Feature #5875: Changes to child estimate...

New

2010-07-12

関連している Redmine - Feature #6117: subtasks default to paren...

New

2010-08-12

関連している Redmine - Feature #10989: Prevent parent issue fro...

Closed履歴#1 - 2013-03-25 17:35 - Dipan Mehta
Different issues which discuss about linking child issues with parent:
1. Target Version:
There are number of Issues that request linking sub-tasks' Target version to be same or linked to parent's Target version: See #6117 and #9972(Also see http://www.redmine.org/boards/4/topics/28743)
2. Blocking of parent by child issues. see #5462
3. Watchers: Another linkage is to have watchers to be directly inherited. See #7057, #11177.
4. Issue status: #9991, #7450, #5734
5. Time and Estimates: #5733, #5875#2 - 2013-04-10 15:22 - Dipan Mehta
Another important related issue: #6117#3 - 2014-07-14 09:34 - Edosoft Factory
You should checkout Subtasks Inherited Fields Plugin at https://github.com/edosoft/redmine-inherit-fields-plugin#4 - 2015-02-13 20:12 - Bryn Jeffries
Edosoft Factory wrote:
You should checkout Subtasks Inherited Fields Plugin at https://github.com/edosoft/redmine-inherit-fields-plugin

Great plugin. In addition, to retrospectively inherit target milestones you can issue via the database console (at least for PostgreSQL)UPDATE issuesSET fixed̲version̲id=I2.fixed̲version̲id
FROM issues I2
WHERE issues.parent̲id=I2.id;#5 - 2015-07-08 13:19 - Ricard FThis would be great to have it nativelly... There is nothing simillar to that plugin working on 3.X#6 - 2015-07-16 10:19 - Jérôme L
Maybe proposing parent values as default is not enough. What if a parent value (say, milestone, for example) changes? Should the child valuechange as well?
For each potentially inherited property, the choice should include "Inherited from parent" and this link should be remembered instead of the value
itself. This could be the default choice.
This way, the user can choose to have a property of the child issue (priority, version) differ from its parent property, but if it is set to be inherited,changing the parent's property changes the child property as well.
#7 - 2015-10-01 13:33 - Florian ROBERT+1#8 - 2016-02-02 13:13 - Alessandro Zucchi+12024-09-08

2/3

#9 - 2016-09-20 14:11 - Toshi MARUYAMA- 関連している Feature #10989: Prevent parent issue from being closed if a child issue is open を追加#10 - 2016-09-20 14:11 - Toshi MARUYAMA- 関連している を削除 (Feature #10989: Prevent parent issue from being closed if a child issue is open)#11 - 2016-09-20 14:12 - Toshi MARUYAMA- 関連している Feature #10989: Prevent parent issue from being closed if a child issue is open を追加#12 - 2016-09-20 14:13 - Toshi MARUYAMA- 関連している を削除 (Feature #5462: Blocking issues to be closed which have open subtasks)2024-09-08

3/3