Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Any way to have two possible transitions configured for the Approve action?

We have a user that wants the same workflow to have a state configured for approval that then conditionally goes to either one state or another upon the user clicking the "Approve" button.

He wants the "Approve" transition to go to either state X or state Y depending on the value of a custom field.

As far as I can see, the transition configured for "Approve" is required to be just one transition, not conditionally one transition or a different transition.

Please advise if this is possible, even if it means using an automation rule or some other trick that is outside of the workflow itself.

3 answers

1 accepted

0 votes
Answer accepted

JMWE 7.0.0.1 has new event driven workflow - you can transition a workflow, for example, based on another transition, a comment to an issue, a change in field value, etc.

I tested it, it works, and doesn't have the limitations of "Automation Lite for Jira"

2 votes
Carlos Faddul Community Leader Oct 29, 2021

@Ken Wood  you can create a second status to approval then use the automation to auto approve in this status.

But all approvals only have Two options (approve/reject) then you can create you workflow basead in this options or in custom fields with conditions (to dodge of approval status)

I tried using "Automation Lite for Jira" and the problem is, 

"Please note that rules triggered by 'Issue created' or 'Issue transitioned' and containing a 'Transition action' cannot be executed immediately. This is due to limitations with Jira's workflow engine. See JRASERVER-40597 for more details."

So that means the rule fires in the background and so in the browser the user sees the issue in the waiting for approval state instead of the state it was auto-transitioned to.

There is an action to re-fresh, but it says "This action does not reload the issue in the browser for end-users."

So I don't see this as a solution, at least using Automation Life for Jira.

1 vote
Mikael Sandberg Community Leader Oct 29, 2021

Correct, the approval can only have one transition each for approve/reject. You could use Automation or any of the other automation apps in the marketplace to achieve this with the conditional status, just add status Y in the workflow and then move to it after the request has been approved and the custom field has the right value.

Friday I tried using "Automation Lite for Jira" and the problem is, 

"Please note that rules triggered by 'Issue created' or 'Issue transitioned' and containing a 'Transition action' cannot be executed immediately. This is due to limitations with Jira's workflow engine. See JRASERVER-40597 for more details."

The rule fires in the background and so in the browser the user sees the issue in the waiting for approval state instead of the state it was auto-transitioned to.

There is an action to re-fresh, but it says "This action does not reload the issue in the browser for end-users."

I don't see this as a solution, at least using Automation Life for Jira.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira Service Management

Next level incident management in Jira Service Management

Hello Atlassian Community! We’re thrilled to announce some exciting changes to incident management in Jira Service Management Cloud, in order to give your teams extra muscle during incidents, and ...

1,741 views 21 12
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you