Roll up Subtask Estimates and Time Tracking to Parent Task for Workflow Conditions

[Yossi Geretz]

I have two conditions for changing the status of a task to Done.

   1. The task must have an estimate

   2. The task must have some amount of time spent

I'm finding that, when completing all the subtasks, the parent task itself can't be transitioned to Done because the Parent Task doesn't have its own independent estimate and time tracking.

How do I change "Original estimate" and "Time Spent" in the following conditions to refer to "value for task or child subtasks"? (As a workaround, I'm adding an estimate and time spent of of 1 minute to each parent task, but this is such an ugly workaround.)

[Stefan Salzl]

Hi @Yossi Geretz 

Not knowing exact details but as it seems to me I assume both issue types have the same workflow.

The easiest way (without any plugin) would be to have 2 different workflows (which is very common for standard and sub-task issues).

If you have scriptrunner plugin installed you could add a scripted condition that checks the current issue type and only validates true for subtasks.

Best
Stefan

[Yossi Geretz]

Thanks Stefan for the suggestion, however that is a bit too simplistic. There are actually four use cases, not two. I'd need different rules for:

1. Subtasks: must always have an estimate and time logged.

2. Tasks (other types):

    2a. IF the task has NO subtasks, then it must have its own estimate and time logged.

    2b. IF the task does not have its own estimate and time logged, it has subtasks but none of those have estimate and time logged (can't be marked Done)

    2c. IF the task has subtasks and it has its own estimate and time logged OR at least one subtask has an estimate and time logged. (Can be marked Done)

It would be much more natural if the parent task would have a pair of logical attributes (e.g. totalOrigEstimate and totalTimeSpent) which would take care of all of these basic rollup calculations. I think this is a fair ask. Is the relationship between a parent task and its subtasks hierarchical or not? If yes, then work quantities defined for subtasks should roll up to the parent task and be accessible as attributes of the parent task.