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

Workflow status changes -- moving back to previous status only

Debbie Buswell

Hello,

We have a worklfow that allows transitions from 1 status (Blocked) back to 4 other status (QE, Ready for QE, Development, UAT). The workflow need to check that when the status is changed from Blocked to one of the 4 statuses it goes back to the original status only. (Example: Development ---> Blocked ---> Development)

What is the best way to do this?

So far, using boolean as a condition has not worked. Getting syntax errors and not able to debug.

Thank you for your help.

Debbie

Accepted answers

Debbie Buswell

Hello,

An update.

We were successful in using JMWE to write a validator to check the current, last status from and last status to in order to check if the user was returning to the correct status. The groovy script is in every status that can use the Block status in the workflow.

All comments

Petter Gonçalves

Hello Debbie,

You can use the Previous Status Condition to each transition in your workflow, so it will ensure that the last status that your issue was transitioned from is the same that it's being moved to.

To do this, you must perform the steps below:

- Navigate to your project > Project settings > Workflows

- Click to edit your workflow

- Click on the transition that comes from the status Blocked to Development > Click on Conditions > Add the Previous Status Condition

- Ensure that the previous status of the issue was Development to allow this transition

- Repeat the same steps for:

Blocked to QE

Blocked to Ready for QE

Blocked to UAT

- Publish your Workflow

P.S: When configuring the Condition, don't forget to flag the option to apply the condition only for the previous status of the issue.

Debbie Buswell

Petterson,

Thank you for the reply.

I am on JIRA 7.84 and have JSU. I do not see Previous Status Condition in the condition list page. Is this a plug-in or a built-in feature of JIRA?

Below is a list conditions available.

Thank you for your help.

Debbie

Conditions:

A field is/isn't initialized

Boolean condition with math, date-time or text-string terms

Cascading select comparer

Check project property

Code Committed Condition

Compare two parsed texts

Complete session condition

Condition based on JQL query

Condition based on regular expression

Condition on a list of issue keys

Condition on linked issues

Condition on subtasks

Except assignee

Except reporter

Except users in a field

Hide transition from user

No Open Reviews Condition

Only Assignee Condition

Only Reporter Condition

Only users in a field

Permission Condition

Sub-Task Blocking Condition

Transition is triggered by Bulk Operation

Transition is triggered by Jira Workflow Toolbox post-function

Unreviewed Code Condition

User Is In Any Groups (JSU)

User Is In Any Roles (JSU)

User Is In Custom Field (JSU)

User Is In Group

User Is In Group Custom Field

User Is In Project Role

User is not in project role

Users in a field are/aren't in a project role

Value Field (JSU)

Payne

Ah, you have the JSU add-on, so try "Value Field (JSU)" and configure like this:

https://confluence-apps.beecom.ch/display/JSU/Value+Field+Condition

Debbie Buswell

Payne,

Thank you for the reply.

Is Prior Status a custom field in your JIRA?

This is not a valid field for "my" JIRA.

Debbie

Debbie Buswell

Hello,

An update.

Jositz, Michael (Allianz SE)

I guess you can use JSU with "JQL Condition (JSU)" like this:

issuekey = {issue.issuekey} and status was "XY"

Plus stating that "Particular number / More / Less" has to equal 1.

Eric Sebian_8o0yik

can you provide the groovy script?

Welcome!

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

Quick Links

Find more posts tagged with

jira