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

Adding multiple conditions to Issue transition in a JIRA workflow - RESOLVED

Prashant Deshmukh

Hi,

I am trying to enforce some conditions for transitioning a JIRA issue in a workflow.

I have following transition steps in a Workflow named BugWorkflow

1. Open

2. In Progress

3. In QA

4. UAT

5. Close

I have several fields in my Bug Issue scheme. I want to check conditions on following non-mandatory custom fields a) SVN version b) Front End Code Reviewed c) Back End Code Reviewed

Here is what I want to do, When someone tries to transition a JIRA issue from UAT -> Close

I want to check

If SVN version field is empty - >Close the issue

Else check

If ( Front End Code REviewed is Empty OR BackEnd Code Reviewed) ->Close the issue

I know that I can add single condition but this is a bit complex. If you have any solution, please let me know

Thanks

Prashant

Accepted answers

Sreenivasaraju P

You can use value field condition and add any level of grouped conditions.

All comments

Sreenivasaraju P

You can use value field condition and add any level of grouped conditions.

Prashant Deshmukh

Hi @Sreenivasaraju P,

Thanks. Sorry for the late reply, I have tried your solution but its not working for me yet. I wanted to compare both NULL and not null condition at the root level.

If I can write some psudo code, I Here is what I am trying

If( SVN == NULL)

{

IF (Back End Code Reviewed == NULL OR Front End Code Reviewed == NULL)

{

Close JIRA issue

}

ELSE IF (SVN !=NULL)

{

IF (Back End Code Reviewed != NULL OR Front End Code Reviewed != NULL)

{

Close JIRA issue

}

I am not able to put the second condition somehow.

This image help you understand better. Appreciate your help in this regard.

Thanks

Prashant

Prashant Deshmukh

I could change this a bit but still not able to achieve the expected outcome. Here is how it looks now. I guess the external nesting (pointed by red arrow) is causing the problem. Do you see any solution?

Thanks

Prashant

Nic Brough -Adaptavist-

I suspect it's because your nesting is not doing anything.

At the top level, you have two condition groups joined.

The first group says "The field fixed in svn version # ... equal to null". The second says "The field fixed in svn version # ... not equal to null". As the join is "any", then you are going to find that every issue matches the joined condition.

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-cloud

jira-administration

workflow

condition