|
History
| Log In
|
|
|
|
It would be very useful to have particular fields (not necessarily those already mentioned) inherit from the parent task. This would have the added benefit that the field would not need to be displayed on the screen, thus preventing the user changing the value of an important field.
We'd really like to inherit the component from the parent task (or be able to select component, defaulting to parent's)
Has there been any movement on this issue at all? I remember once being told on the mailing this would now available somehow but I can't find a reference to it
I was also thinking that if any of the inherited fields are changed upstream (and not changed locally on the subtask) then whenever the parent issue is changed those field changes should propagate to the subtasks. i.e. create a ticket with fixFor 3.3, add 5 subtasks (defaulting to 3.3), push out the change to 3.4, all the subtasks should update to 3.4. I'm doing this now with a listener. The workflow post function would do it for transitions, but doesn't catch if the issue is just edited. Unless I'm missing something. There's a few times that a post function on the edit would be nice. But I guess that's a different issue
 In addition, a Parent Issue should be able to host a view of fields in its sub-task(s).
Think of it as a sub-task Portlet. Cheers - Jordan This would help with test case management from Jira when the subtask is a test run and should reflect enough fields from the test case parent issue so know what the test run is testing. Would really like to be able to specify which fields (standard and custom) are inherited.
I guess the best option would be to allow user to tick those parent issues fields which values they would like all sub-tasks to inherit even on edit or assign.
For instance, if I would like to ressign paernt issue to another person I'd like to be able to indicate if needed that all its sub-tasks to be atomatically reassigned to the same person Just to clarify, what I requested in this issue is something quite simple - that newly created subtasks have most fields set by default to the same value as the parent task.
Easy to implement (I would expect) and a real time saver. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Improvement
Open
Major
Subtask should inherit (some) fields from parent task as default values
It certainly makes sense to inherit these fields from the parent task as you would imagine they will be the same in > 90% of the cases.
Cheers,
Nick