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

Is it possible to block a workflow transition based on values in custom fields?

Kara Nadarajah

Here is the use case:

I have 4 custom fields:

Compliance sign-off required (Yes/No)

Business sign-off required (Yes/No)

Compliance sign-off by (Name)

Business sign-off by (Name)

If, when transitioning a ticket to 'Resolved', 'Yes' has been indicated against either 'Compliance sign-off required' or 'Business sign-off required' and an associated name has not been populated, I want the transition to be blocked. This is to stop changes being deployed to production which have not been fully signed off in our pre-prod environment.

Is this possible?

Accepted answers

John Funk

Hi Kara,

Yes, you can put conditions on the transitions of the workflows to block them if the values are not set.

All comments

John Funk

Hi Kara,

Yes, you can put conditions on the transitions of the workflows to block them if the values are not set.

Kara Nadarajah

Great, how do I do it? I had a look at the workflow settings but I couldn't work out how to block the transition only in the following scenario (in that it only matters if the field is null when the other field is 'Yes'):

Given custom field A = Yes

When custom field B is null

Then block transition 'Resolved'

John Funk

Do you have a separate transition called Resolved? Or is that just a value in the Resolution field for the transition to Done?

If the transition is indeed called Resolved, then add two conditions to the transition.

Select Value field for the condition and click Add.

Choose Custom Field A from the dropdown list

Choose = for the condition

And put Yes in the value field.

You can do the same for addition a second condition, except leave the value field blank for null.

With these two conditions, the transition for Resolved will not be visible unless both conditions are met.

Kara Nadarajah

Thanks. So I have added these rules, but I am a bit confused.

How does the system know that the second condition is dependent on the first? I am failing to identify how it is linked?

Also, I don't want to block the issue being 'Resolved' if the value entered is 'No' rather than 'Yes'. If 'No' is entered then then custom field B will always be null...

Screenshot 2020-09-28 at 14.15.59.png

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-software

jira-software-cloud

jira-cloud

transition

workflow