How to add approval step in workflow in jira software

Ayush Pathak April 27, 2024

I need a step-by-step guide on adding an approval step in Jira Software for issues with high or highest priority. I'm using the Time to SLA app, which should only initiate after approval from the head department is accepted. Otherwise, the issue will be closed.

4 answers

4 accepted

2 votes
Answer accepted
Michel Neeser
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 27, 2024

Hi @Ayush Pathak

In Jira Software, approval steps are generally configured by using one of the following user conditions on a transition:

SCR-20240427-lvuz.png

This way, you can limit which users are able to execute a certain transition and who can put an issue in a certain status.

Hope this helps!

Ayush Pathak April 28, 2024

Thankyou @Michel Neeser 

Michel Neeser
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 28, 2024

@Ayush Pathak Glad I was able to help! Please consider accepting the answers that were helpful to you, maybe they will support others in the future as well. Thank you!

Ayush Pathak April 28, 2024

Sorry about that, @Michel Neeser . I forgot to accept the answer before, but I've done it now. It was really helpful.

0 votes
Answer accepted
Alexis Leites April 27, 2024

Natively with buttons, as we have in JSM, it is not possible.

Maybe this article can help you:

Add an approval step using Jira Software and Work Management

I understand that with the Time to SLA app you can set a condition to start the SLA when it transitions to the ''approved'' state.
 


Ayush Pathak April 28, 2024

Thankyou @Alexis Leites 

0 votes
Answer accepted
Fabio Racobaldo _Herzum_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 27, 2024
Ayush Pathak April 27, 2024

Is this free?

0 votes
Answer accepted
Jack Brickey
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 27, 2024

Hi @Ayush Pathak , 

I want to ensure you are talking about JSW here and not JSM. For the remainder of my response I will assume JSW. Also, I am unfamiliar with Time to SLA so I cannot instruct you in that regard but would assume that it must have some configuration that allows an SLA to start when entering a certain status which would work well with the below approval process. Finally, I am providing a guide for Company managed software projects. If you are using Team managed this will not apply.

 

the concept here is that you will modify the workflow to add approval process statuses: awaiting approval, approved, rejected, along with user transition restrictions from the "awaiting approval" to either of the approval results statuses.

  1. Create a copy of your workflow and name it uniquely 
  2. edit the workflow and a status named Awaiting Approval. Assuming every issue goes thru this approval unconditionally, then this status should be the initial status when it the issue is created. In that case relocate the create transition to this new status and delete the old status. For the other two statuses you can either use existing statuses or create new ones. For example for the Approval rejection you could use your done/closed status. If you do that I recommend adding a post function to the transition to set the Resolution field to "rejected" so that you will be able to assess stats on rejected issues. For the "approved" status you could use any status that would convey approval, e.g. to do, in progress, etc. of course you could add a new Approved status if desired. Note, this approved status would be used for starting your SLA.
  3. Next you will need to associate your workflow to the desired issue type. However, you may wish to use a 'test' issue type to test the process before assigning the workflow to the actual issue type.

this should get you going.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events