nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Automation condition to transition parent status based on subtask approval

AT_qbizjp

I want to create an automation (for a company managed project) where story/bug issue type can transition from To Do state to In Progess only if 1. subtask approval is present AND 2. subtask approval is approved. If the sub-task approval is missing OR if it is not approved, I am thinking the 'In Progress' state will simply not be present in the state dropdown.

Thanks!

Accepted answers

Giovanni Melai_uleent

HI @AT

What you described is not an Automation but a Transition Condition in the Workflow, in this case in the workflow of the Story/Bug.

I can think about one way to do it out of the box even if maybe not the best.

What you can do is use the "Sub-Task Blocking Condition" where you can select the statuses you want the subtasks to be for the transition to be available to the user.

A pre-condition is that you should automatically create the Approval subtask when the Story/Bug is created, so you are sure it's always present, this won't work if the Approval subtask does not exist.

You should then define dedicated Statuses for the Approval Subtask (like "To be approved" and "Approved"), that you are not going to use in other Subtasks in the same project.

Now you can create the "Sub-Task Blocking Condition" and select all the statuses except "To be approved", in this way the transition will not be available only if the Approval Task is in that status.

Said this, I'm not sure if this is the best approach to managing approvals in a Software project, I would instead add an approval status in the Story/Bug workflow, maybe before "To Do" and limit the transition from that first status to "To Do" only to the specific people that should have the ability to approve it. You can do this based on a project role or a Jira group.

I hope this helps

All comments

Giovanni Melai_uleent

HI @AT

What you described is not an Automation but a Transition Condition in the Workflow, in this case in the workflow of the Story/Bug.

I can think about one way to do it out of the box even if maybe not the best.

What you can do is use the "Sub-Task Blocking Condition" where you can select the statuses you want the subtasks to be for the transition to be available to the user.

You should then define dedicated Statuses for the Approval Subtask (like "To be approved" and "Approved"), that you are not going to use in other Subtasks in the same project.

Now you can create the "Sub-Task Blocking Condition" and select all the statuses except "To be approved", in this way the transition will not be available only if the Approval Task is in that status.

I hope this helps

AT_qbizjp

Thank you for the response Giovanni.

So we do a have an automation now so that any time a story or bug issue is created, a sub-task approval is automatically created. The states used in sub-task are unique to sub-task.

My question for you is from where and how do I create a sub-task blocking condition?

This is company managed project so I cannot directly add conditions in the workflow (it is set to read only as many project used the same workflows). However, I can use automation for my project. I tried using following automation, but it still allows to change the parent story/bug status to In Progress, even is sub-task is not approved.

Subtask approval.png

Giovanni Melai_uleent

If you cannot change the Workflow you are not able to achieve what you have in mind. Because the workflow condition is the only way to block the transition, with Jira Automation you can only act after something happened.

You should ask your Jira Administrator to configure a dedicated workflow for your needs.

The only thing you can do with Automation is when someone transitions a Story/Bug to "In Progress" you can check if there is an approved Approval subtask and if it's not the case you can automatically transition the Story/Bug back to "To Do", maybe also adding a comment mentioning why it was moved back.

I hope this makes sense

AT_qbizjp

Unfortunately, due to scale of JIRA we use at our organization getting this approval to allow changing workflow condition will likely not happen.

Your response on automation is helpful. Can you help me figure out how do I set the variable for this transition to happen. This would meet what I am trying to achieve.

Pls check the screenshot I shared before. That automation conditions are not doing what I wanted. Subtask approval.png

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

automation

sub-task