Page Comparison

When you add this validator to a transition and trigger the transition, the add-on checks the number of related issues of specified link type added on the transition screen against the number of issues entered in the Min. Related Issues field. If it does not match then an error message is displayed. 

You can further customize the validation using the following options:

What to validate

Require the creation of issue links on the transition screen: The transition cannot proceed further if at least one issue of the specified link type and respecting the constraints (explained below) is not linked to the current issue on the transition screen. 

For example: To validate during a transition that at least one issue with “causes” link type is linked

Validate that issue links added on the transition screen are of the specified link type: The transition cannot proceed further if the issue links added on the transition screen if any, are not of the specified link type, and do not respect the constraints (explained below).

For example, Validate during a transition that issue links of “is blocked by” link type are “Bugs”

Validate issue links added on the transition screen, if they are of the specified link type: The transition cannot proceed further if issue links of the specified link type when added on the transition screen, do not respect the constraints below.

For example: Validate during a transition that issue links of “is blocked by” link type when added are assigned

Require certain related issues: The transition cannot proceed further if related issues respecting the constraints below do not exist. If the relationship is based on issue links ("blocks", "is cloned by" etc), these issue links can either already exist or be added on the transition screen.

For example, Validate during issue creation that a Story is linked to an Epic

Check related issues: The transition cannot proceed further if existing related issues of specified link type do not respect the constraints below. If the relationship is based on issue links ("blocks", "is cloned by" etc), these issue links can either already exist or be added on the transition screen.

For example, Validate during a transition that the issue has subtasks

Forbid certain related issues: The transition cannot proceed further if related issues respecting the constraints below exists. 

For example. Validate during closing an issue there are no blocked issues.

Issue link

Select the link from the Issue Link drop-down, or leave it as Any for any link type. Applicable to options "Require the creation of issue links on the transition screen" and "Validate issue links added on the transition screen, if any" of Related Issues Validator#What to validate section

Which issue(s)

Applicable to options "Require certain related issues" and "Check related issues" of Related Issues Validator#What to validate section. Select the issues to check the constraints on. They can be:

• Linked issues: Select issue(s) linked to the current issue through any link type or a specific link type such as blocks, is cloned by, etc.

• Sub-tasks of the current issue: Select this option to operate on the sub-tasks of the current issue

• Parent issue of the current sub-task: Select this option to operate on the parent of the current issue

• Issues that belong to the current Epic: Select this option to operate on the issues that belong to the current Epic

• Epic of the current issue: Select this option to operate on the Epic of the current issue

• Child issues of the current issue in the Portfolio hierarchy: Select this option to operate on the child issues of the current issue in the Portfolio hierarchy

• Parent issue of the current issue in the Portfolio hierarchy: Select this option to operate on the parent issue of the current issue in the Portfolio hierarchy

• Issues returned by a Groovy script:  Input a Groovy script that returns either a single Issue object, or a Collection of Issue objects, or a String representing the key of an issue, or a Collection of Strings each representing an issue key. For example:

  • "TEST-1"

  • ["TEST-1","TEST-2"]

  • ComponentAccessor.issueManager.getIssueObject("TEST-1")

  • [ComponentAccessor.issueManager.getIssueObject("TEST-1"),ComponentAccessor.issueManager.getIssueObject("TEST-2")]

  • issue.parentObject

  • issue.getLinkedIssues()

• Issues returned by a JQL search:  Input a JQL search expression, including an optional Groovy Template markup. For example:

  • project = TEST returns issues of the project with the key TEST

  • project = ${issue.get("project").key} and assignee = ${currentUser.name} returns issues of the project the current issue belongs to and assigned to the current user.

  • To operate on issues of a project with key TEST and issue type name same as the value in a text field

    Code Block
    <% if (issue.get("Single line text")) { %> project = TEST and issuetype = ${issue.get("Single line text")} <% } else { %> issuekey=INVALID-1 <% } %>

Issue constraints

Min. Related Issues

Select the minimum number of related issues to be accepted. By default, it is 1.

Max. Related Issues

Select the maximum number of related issues to be accepted. Leave it blank for no limit.

Condition on related issues

Input a Groovy condition in this field to check on each related issue. Leave blank if you don't need any constraint on the related issues. See the Groovy editor help for more information on writing the Groovy condition.

All related issues must verify the condition above

By default, this option is checked and the Groovy condition written above is checked on each related issue of the current issue. If you uncheck this option, at least one related issue, instead of all, must verify the condition.

Validator Scope

Control the execution of the validator using this option. Check this option if you want the validation to be performed only in certain cases, such as if the issue is of certain issue type or only if the issue is unassigned, or more generally satisfies an arbitrary Groovy expression.