Error formatting macro: appfire-confluence-analytics: java.lang.NullPointerException: Cannot invoke "com.atlassian.confluence.xhtml.api.MacroDefinition.getMacroId()" because "macroDefinition" is null
Skip to end of banner
Go to start of banner

Conditioned Validator - 4.x

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

Description

Conditioned Validator is a validator that supports powerful regex pattern matching conditions including JQL query and Substitution variables similar to the Update issues and Create on Transition for Jira post functions. A JQL query can be useful to determine the existence of issues or to find specific issues to participate in the determination on whether to proceed with the transition.

The configuration of this validator is grouped into the following configuration settings tabs:

  • Conditions & Configuration - Allows you to define one or more conditions, each of which must be satisfied (true) for the transition to proceed. If not, an error message is displayed to the user.
  • Messaging - Allows you to enter useful information for the user or notes for the administrator about the validator.

Variables used in validators

Validators are more likely to use the transition variables to access the screen values since the issue field values still represent the former values. Use original to prefix substitution variables not on the transition screen and transition to prefix substitution variables that are on the transition screen.

Add Conditioned Validator

Select Validator

  1. Click the Add Validator button in the Validators section of the workflow transition you want to apply validation on.
  2. Find and select the Conditioned Validator in the list.
  3. Click the Add button to add the validator to the selected transition.

Add Details

  1. Enter the following details in the Conditions & Configuration tab:
    1. "Original_Priority" in Condition 1 and "Blocker|Critical" in the corresponding Regular expression pattern field.
    2. "jql_result_count" in Condition 1 and "0" in the corresponding Regular expression pattern field and select Negative.
  2. Select the Messaging tab.
  3. Enter the following:
    1. "For this issue, the issue must have Blocker or Critical priority and at least one sub-task. Issue priority - "original_priority"" in the Message field.
    2. "Notes for the function" in the Notes field.


View Validators

When viewing all validators, helpful information is displayed.



  • No labels