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

How do I stop an issue from transitioning status before everyone approves?

Christian Bellmore

I’m trying to create an automation rule for moving issues to done once they’ve been approved by all parties. The one I created works well for the most part, but if there’s multiple approvers on a task, it doesn’t wait for everyone to respond--say that another person and I are approvers. If only I approve the issue, it’ll go straight to the approved status without input from anyone else. approval auto 1.png

It should be noted that my company doesn’t use Jira Service Management (and based on what little I know about JSM and what this rule will be used for, I don’t think that would benefit us). We use Jira Software.

I created a custom field called “Approval Status” and used the trigger When: Value Changes and added conditions for it to transition to different statuses depending on what was selected. I tried adding an Advanced Compare Values to the If/Else section, but nothing really worked (doesn’t matter how much I learn about them, I don’t think I’ll ever wrap my head around Smart Values lol). approval status 2.png

So, does anyone have any suggestions on how to fix this so that the issue doesn’t transition before all approvers respond?

Accepted answers

All comments

Bailey Hecksel

@Christian Bellmore I think you want to attack this from the Workflow instead of Automation. If you take a look at the approval step in your workflow, you should be able to set "number of approvers" and select which statuses to transition to for Approved/Declined.

Let me know if this helps.

Christian Bellmore

Hi @Bailey Hecksel. I think that's only available in JSM. This is what it looks like when I tired to set that in my workflow. I tried the out of box status to see if that made a difference, but it didn't make a difference

approval workflow.png

Bailey Hecksel

Wow, I think you're right. That seems incredibly silly to me.

If JSW and JSM projects can utilize the same (global) workflows, why is it not available in JSW?

Sorry for any confusion.

Christian Bellmore

Don't worry about it. I appreciate the help either way And yes I agree, it doesn't make sense that this isn't an option in JSW! I hope Atlassian adds it someday

Kian Stack Mumo Systems

@Christian Bellmore,

Great question.

I think I've got something that may work for you.

First, you'll need two custom fields

The "approvers" field which should be a multi user picker field.
A number field to store "approval count"

Let's say you have a status called "Waiting for Approval". On that status, create a new transition that goes from Waiting for Approval -> Waiting for approval.

On the transition, set a condition that only users in the custom field you created can execute the transition. You'll also want a transition for Rejecting the approval. You can just make that one go to the status that a rejected ticket would go to. Once again, add a condition so it can only be done by users in the approvers field.

Once you have those two, you'll want to create a 3rd transition from your "waiting for approval" status -> Change request approved. On this status, set a condition to "hide" the transition from the user.

Now we'll get into the automation rule. Basically what we will do is increment our "Approval count" each time the "Approval" transition is executed. After every increase to the field, we re-fetch the issue data and check to see if we have the same number of approvals as people in our list. If so, transition it to the "approved" status.

My automation rule just uses some dummy statuses, but you can just update it with your values and it should work no problems.

Screen Shot 2023-08-11 at 4.11.49 PM.png

Christian Bellmore

Hi @Kian Stack Mumo Systems. Thank you so much for this. The workflow part has been working, but so far I haven't gotten the automation to work in my favor. I'm thinking what I want is too complex for Jira automation and that I'm going to need an add-on Oh well. Thank you again for your help though, I really appreciate it!

Kian Stack Mumo Systems

Which part isn't working?

Thanks,

Kian

Christian Bellmore

Well, the “Edit issue Fields: Approval Count” doesn’t actually wait for multiple people to respond. It just, er, changes whatever number was in the status on the issue? Like if I had a 1 there, the number would increase to 2. I tried multiple combinations and I keep getting the same result (besides when I added >=1, but even then, it wasn’t really waiting as more of it just wasn’t changing the value).

I can get the status to transition to “Approved” … even if I pick the “Rejected” approval status. Nothing I do can get it to move to “Not Accepted”. I even tried splitting them up so that there’d be an accepted rule and a rejected rule, but it still wouldn’t move and said there was an error. And if I try to make a rule with both aspects included, it just doesn’t transition to anything whatsoever!

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

automation