Create 3 auto sub-task when the parent status changes

Christian Ggrigoras

All,

I'm created a workflow and cannot proceed forward.

I would like to the following  :

1. Task in status:'Intake' move in status:'Approve' then in the same time 3 sub-task should be created with a specific name and all 3 of them should have 'Approve' status.

      2. When all sub-task are in status 'Approved' I would like that the task status to change into 'Review'.

 

Hope you can help me out.

Thanks in advance.

Christian

 

Rusi Popov

Hello Christian,

In our company we are facing a similar problem. Our solution is to use an Issue Event Listener and the logic is complex enough.

Here is why the pure post-functions and conditions approach does not work (and the listener approach is applied):

• Step 1 is quite straightforward and could be implemented with custom post-functions.
• Step 2, specifically the requirement to coordinate the  sub-tasks and when they complete to make a transition on the parent task cannot be implemented as post-functions and condition as:
  • in order to coordinate the sub-tasks, they just have to attempt to transition the parent task
  • the parent task should make the transition only if all its sub-tasks are completed. This is a pure condition on that transition
  • attempting a transition, that is not allowed makes JIRA throw an exception, which rolls back the current transaction  - this is the general transition validation mechanism of JIRA
  Then:
  • when the first sub-task completes, a post function on its transition to complete could attempt transitioning also the parent task
  • from the point of view of the sub-task, this transaction should succeed
  • from the point of view of the parent task, this transition is not allowed, its condition fails and the transaction rolls back.

This shows that the pure condition & post-functions approach does not work.

In contrast, the issue events in JIRA workflows are processed out of any transactions, which allows the sub-task's transition to complete successfully, isolated from the transition (if any) of the parent task.

Then, a Issue Event Listener approach could be:

• listen for a General Issue Event (#13),
  
  • if the firing issue is a sub-task (of your specific types) then
    
    • find the workflow of the issue that fired the event
    • if it is a transition to DONE state, then:
      • find the parent task
      • transition it

The knowledge how to implement such logic is quite well provided in the recipes in "Jira 5.X Development Cookbook" by Kuruvilla.