Condition a workflow transition based on statuses of all other issues on the same project


I'm trying to figure out how to add a condition to a workflow transition to make sure the transition can only take place after all other issues on the same project are closed (or resolved).

Can anyone help?



5 answers

1 accepted

0 votes
Accepted answer

Hi Ronen,

There is an indirect way to do it using JIRA Workflow Toolbox's project properties:

1.- Create a property in your project called "OpenIssues" containing the number current of open issues in the project.

2.- Add in issue creation transition and issue reopening transitions the following post-functions:

- Read project property "OpenIssues"

- Increase the read number.

- Write the increased number into project property "OpenIssues"

3.- Add in all the transitions closing or resolving the issues the following post-functions:

- Read project property "OpenIssues"

- Decrease the read number.

- Write the decreased number into project property "OpenIssues"

You can check the value of the project property "OpenIssues" in any transition of the workflow using available condition and validator in JIRA Workflow Toolbox.

IMPORTANT WARNING!!! You shouldn't allow to move issues to this project, because the project property "OpenIssues" won't be updated.



Thank you fidel.

It's a good answer although I hoped for a feature that can list all issues of the same project (which should be similar to list all linked issues).

Maybe a feature request for the next version? :-)

Thank you,


You can bet on it!!! Maybe in 2 weeks.



Hi Ronen,

With recently released version 2.0.8 of JIRA Workflow Toolbox, you can implement a more direct solution for you question. You will need to use condition "Condition on non-linked issue" or validator "Validation on non-linked issue" and virtual field "Issues in current project".

The following screenshots shows a possible solution that requires that all bugs, improvements and new features in the project are resolved or closed for the transition to be triggered:



I hope the solution is clear enough,


Fidel Castro Armario.

"Condition on non-linked issue" and validator "Validation on non-linked issue" has been renamed in most recent version of the plugin to "Condition on a list of issue keys" and "Validation on a list of issue keys".

Since version 2.1.26 of JIRA Workflow Toolbox, field "Issues in current project" is renamed to "Rest of issues in the project".

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Feb 07, 2019 in Marketplace Apps

A Timeless Love Story

It started as any story starts, on a normal, rainy day.   Admin meets App, and her name was Klok2, and like any first relationship we were both trying to make it work but neither one knew what...

460 views 8 27
Read article

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you