Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,368,846
Community Members
 
Community Events
168
Community Groups

Three Different 'Approval' Flows from Peer Review

Hi there,

I have a situation where I am building a change flow where after Peer Approval there are three possible outcomes

Normal Change - Low => Straight to Awaiting Implementation

Normal Change - Med => Transition to Change Manager Approval

Normal Change - High => Transition to Planning

The only way I could think to handle this was go to a temp status and then run an automation when the issue transitions to that status and then force the transition based on that.

Is there a better way to do this?

ChangeIssue.JPG

Thanks

 

1 answer

1 accepted

Hi Steven,

This is in fact the best way to do it. I did the same thing for a change process too where if it's approved, an automation start on the "temp" status to calculate some fields and call transitions based on the score to determine if it's Low-Medium-High

 

Have a nice day

Frederic

FMX Solutions - Gold Solution Partner

OK thanks for that, I thought I was miles off track with it but couldn't seem to find a way back either.

Appreciate the input (validation :) )

Suggest an answer

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

Atlassian Community Events