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

Skip or follow a transition step based on cutom field value

Rizwan Rizvi

I have a situation here

Normal Flow --------------------- Dev-Requestor-Close

Another flow is ------------------ Dev-Requestor-QA-Close.

Want some way to implement this based on if a checkbox is checked for QA and accordingly follow the route.

Any help appreciated.

Accepted answers

Rizwan Rizvi

I was able to get around this.

Using Script Runner plugin from JIRA Marketplace.

First, created a field called QA testing Required with 2 values 'Yes' and 'No'.

I create 2 transitions by the same name so as not to confuse the user.

1. Script workflow function : Simple scripted condition : Checks script:

cfValues['QA Testing Required']*.value.contains('Yes')

This is now flowing to the QA person.

2. Script workflow function : Simple scripted condition : Checks script: 
cfValues['QA Testing Required']*.value.contains('No')

This skips the QA and follows to the last step.

All comments

C.Faysal {CFcon}

I am kinda confused here. As you are talkin about workflows you may mix sth up ? Please clearify if this isn't maybe a transition thing. If so just add 2 transitions and configure a condition to each of them. Sth like "only show if..." Maybe you will need to install additional plugins to get this https://marketplace.atlassian.com/plugins/com.innovalog.jmwe.jira-misc-workflow-extensions

Rizwan Rizvi

I do get what you are saying but in my case there is a field called 'Set for QA Testing'. Now this feild can have a 'YES' or 'NO' value.

If its YES, I want the flow to be

DEV > Requestor > QA > CLOSE

But if the value of this field is NO, the flow would be

DEV > Requestor > CLOSE.

Does this explain clearly?

Rizwan Rizvi

I was able to get around this.

Using Script Runner plugin from JIRA Marketplace.

First, created a field called QA testing Required with 2 values 'Yes' and 'No'.

I create 2 transitions by the same name so as not to confuse the user.

1. Script workflow function : Simple scripted condition : Checks script:

cfValues['QA Testing Required']*.value.contains('Yes')

This is now flowing to the QA person.

2. Script workflow function : Simple scripted condition : Checks script: 
cfValues['QA Testing Required']*.value.contains('No')

This skips the QA and follows to the last step.

Ram Chavan1

I am having the same situation. Can you please explain your solution in detail.

Rizwan Rizvi

@Ram,

What I essential did in my solution was to create a dropdown field with 2 values 'yes' and 'no'

I made 2 transitions named 'Ready to Test'. One of them ended up with the QA person if the feild was set to YES and if no the issue flowed directly to the end user for testing.

To accomplish the above i.e. which route to take I installed 'Script Runner plugin'.

Then in the workflow. Go to each transition and perform below steps

Click on transition and select 'View Validators'
Click on 'Add' link on the screen
Scroll down and select 'Script Validator'
Click on 'Simple scripted validator' [Built -in Scripts]
Scroll down below condtion textbox
Click on 'Has custom field value equal to'
it will display "cfValues['SomeCustomField'] == 'Some Value'"
Replce the code with my condtions as above.i.e. 'cfValues['QA Testing Required']*.value.contains('Yes')'

I used value.contains as its a drop-down value.

Should be pretty simple once this goes fine.

Alan Williams

Are you sure this isn't a post-function that would fast track to a status based on a custom field?

Janene Hoffmann1

Curious if you've any problems using post function fast track transition or how you got this to work

Janene

Indranil Mondal

This issue can be resolved in much easier way by using 'condition' 'value field'.

unknown

A bit of a hack I was able to get working, was to use the free Automation add-on; https://marketplace.atlassian.com/plugins/com.atlassian.plugin.automation.jira-automation-plugin/server/overview.

By setting up a rule which fires a cron every minute, runs JQL to find issues where my custom field = x, and takes Transition Action to the desired status. It is not instant, but it met our needs and so far works great.

Regis MASSICARD

Well it seems that now you can't create 2 transitions with the same name any more...

Bernd Anderer

What about an additional intermediate status? This status checks the value of the field and transitions the issue to the according target status.

Welcome!

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

Quick Links

Find more posts tagged with

custom-field

transition

workflow

status