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; } } }

Check, if the last sub-task is in status "ACCEPTED", before transit the parent issue

Lukas_jh1ro7

So I try to explain what is the situation: I have an issue, where you need an approval to go further in workflow (transit status). Approval is a subtask. To transit the issue to next status (Risk Treatment) should the last approval subtask must be in status "APPROVED", That means, you might have many approval subtasks, for example you have 2 approval subtasks and the first one is in status "rejected" then the second one thus the last on is in status "approved". In this case you are able to transit the issue to next status (Risk treatment).

If you have just one approval task, which is rejected, you should'nt be able to transit the parent issue, until you create a new approval subtask, which should be then approved.

Is it possible to solve this problem with Jira Automation?

positive approval needed.PNG

Accepted answers

Mark Segall

Hi @Lukas - This is possible, but not with automation alone. Here's what you need:

A mechanism to indicate on the parent issue that sub-tasks are not yet ready. You could use the flag field, a component, label, or custom field
A validator on the appropriate parent workflow transition that when "flagged" (whatever mechanism you chose above) the parent cannot transition
Automation rule that triggers off of the sub-task and branches into the parent to flag/unflag accordingly

All comments

Mark Segall

Hi @Lukas - This is possible, but not with automation alone. Here's what you need:

A mechanism to indicate on the parent issue that sub-tasks are not yet ready. You could use the flag field, a component, label, or custom field
A validator on the appropriate parent workflow transition that when "flagged" (whatever mechanism you chose above) the parent cannot transition
Automation rule that triggers off of the sub-task and branches into the parent to flag/unflag accordingly

Lukas_jh1ro7

@Mark SegallI have to say my project is company-managed business project in Jira Cloud and not software project. So that means, the use of flag field or component ist pretty limited. What can you recommend in tis case?

Mark Segall

Are you a Jira Admin on the instance? That will be critical because you'll need those rights to set the validation rule.

I haven't tried myself, but you may still be able to use flagged. JSM projects don't use the flag feature either, but I'm able to set it with automation and have done so for this exact purpose in the past (actually cements it as a good option because users can't inadvertently muck with it). If it's truly unavailable (even to automation), I'd recommend some type of custom field that is not on the screen config, but available to the field configuration scheme - making it hidden to users.

Lukas_jh1ro7

@Mark Segallyes I got admin rights there. So can you please explain it, what I have to do exactly? I've never used components by the way.

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud