Versions Compared

Old Version 4

changes.mady.by.user Deborah Scott

Saved on

compared with

New Version Current

changes.mady.by.user Pooja Gopalnaidu

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Div
idProductTOC

On this page

Table of Contents
maxLevel1
excludeOn this page
typeflat
separator|

Summary

If you need to validate a transition based on the existence or non-existence of one or more issues determined from a JQL query, then read on! It is very simple to do with a Conditioned validator.

Steps

Table plus
autoNumbertrue

Step

Discussion

Examples

Create a JQL query that will determine if the transition can proceed or not.

  • Test the JQL in the Issue Navigator first.

  • No unresolved subtasks: parent = XXX-1 and resolution is empty

Add a Conditioned validator to the appropriate workflow transition 

  • Assumes you have installed the

CW


Put the JQL query in the JQL Query field

  • It is likely you will need to use one or more substitution variables like %original_key% in place of a specific values you may have used while testing

  • parent = %original_key% and resolution is empty

Condition by how many issues are found by the query

  • %jql_result_count% is the more substitution variable that says how many issues were found

  • Put that value in the Condition 1 Value field

  • Put 0 in the Condition 1 Regex field

  • Likely user cases are:

    • Proceed with the transition if there are 0 issues found - do not select the Negative checkbox

    • Proceed with the transition only if there was at least 1 issue found - select the Negative checkbox

  • All subtasks must be resolved

noformat
Code Block
Condtion 1:
   Value: %jql_result_count%
   Regex: 0


Add a user friendly message that will show if the validator fails

noformat


Code Block
Message: All subtasks must be resolved before you can proceed. The following subtasks are not resolved: %jql_result_list%.


Save the post function



Run a test scenario

  • Use How to get problem determination information to debug your scenario if necessary.

  • JQL errors will be logged in the JIRA application log. Note: This is the most common cause for problems.

  • Remember, the JQL query runs under the user's permission unless you are using Acting user support.


Screenshot

...