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

Automatic State Transition

harshit29dx

I need a workflow, where in I need 3 approvals and after the 3rd approval is attained, it should move to next state. Eg

Approval 1 -> Approval 2 -> Approval 3 -> Ready

Once Approval 3 has reached it should automatically move to Ready state. How can this be achieved efficiently.

Accepted answers

Dirk Ronsmans

Hi @harshit29dx and welcome!

those 3 approvals would they need to be in a sequence or just 3 people that need to approve and then it can go to the next state?

Just 3 people is the easy one and you can just add them to the approvers field, configure a status with an approval step and have it move to the next step on approved.

if a sequence is required and you don’t want to use an additional app you’ll have to use 3 statussen or even more complex a status that will transition to itself until a number is reached (using some automation tool)

All comments

Dirk Ronsmans

Hi @harshit29dx and welcome!

those 3 approvals would they need to be in a sequence or just 3 people that need to approve and then it can go to the next state?

Just 3 people is the easy one and you can just add them to the approvers field, configure a status with an approval step and have it move to the next step on approved.

harshit29dx

Hey @Dirk Ronsmans yes it just needs to be 3 people who will click on approval 1/2/3 in no particular order. But once the person has clicked on approval 3, it should reach Ready state.

Also, approval 1 /2/3 are independent states of the workflow.

harshit29dx

We don;t have approvers field but they are state as the approvers can be dynamic and depends on the day of approval so we want it to be a state.

Ravi Sagar _Sparxsys_

Hi @harshit29dx

If you always have 3 approval stages then create 3 user group fields for those 3 stages. Then add a condition using "user is in group picker" field. If you have ScriptRunner then you can add a custom script condition based on any field to check for approvers (like user picker field). What I also prefer doing is to add an approval date field to keep track of when approval was give. This approach can work only when you have limited number of approvals.

I hope it helps.

Ravi

Ravi Sagar _Sparxsys_

..and I forgot to mention if you have ScriptRunner then you can use "Fast-track transition an issue [ScriptRunner]" on your last approval transition to move the issue to the next status.

Dirk Ronsmans

@harshit29dx ,

Let me first ask a question to what product you are using. I'm assuming you are using Jira Service Management ?

If so there should be a default system field called approvers but you can use another field.

By default, JSM has a concept of approvals built-in.

This below link will explain it in detail on how to set up the approval step itself.

https://confluence.atlassian.com/adminjiraserver/configuring-jira-service-management-approvals-938847527.html

What it essentially means is that you have a status in your flow (or multiple) where the process will hold until 1 or multiple users (that is configurable) give their approval. (the nice thing is also that these approvers could be customers and thus not require a license)

I believe in your case the easiest set up would be to have

a single status in your workflow configured as an approval step.
add the 3 users to your source field (where will the approval step get it's approvers) and you could even set these to a default value. (it does not have to be the default approvers field)
Also then configure the approval step to only go forward when all approvers have accepted
and choose which state to go when approver/rejected (this is part of the set up)

Welcome!

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

Quick Links

Find more posts tagged with

server

jira

jira-server