Skip to end of banner
Go to start of banner

Linked Status Precondition

Skip to end of metadata
Go to start of metadata

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

Compare with Current View Version History

« Previous Version 11 Next »

JSU for Jira Server/Data Center

This is the documentation of JSU for Jira Server/Data Center. If you are using JSU on Jira Cloud, see ourĀ JSU Cloud documentation.

Description

The Linked Status validator checks that linked issues have a particular status. This check will fail if not all of the linked issues (of a certain link type), have the particular status.

For example in the Testing and Fixing Bugs use case, the tester can’t set a test issue to Ok if there are still open bugs for it.

Configuration

You must define the link type and the status.

Example configuration of the Linked Status validator where issues linked as bugs must have either the closed or resolved status.

Do not use this validator in a transition that will be triggered by a Linked Transition. The check will still get the old status of the issue initiating the Linked Transition.

The Linked Status validator can’t be used in the Create transition. This is mainly due to technical reasons where the issue linking is not established and the validator can’t find the linked issues to validate it.

Optional error message

You can define a custom error message for JSU validators to provide a clear explanation of the situation to your users. If you leave this field empty, a default error message from Jira will be displayed on validation errors.

Example

Bug BF-25 has not been fixed; it is still in IN PROGRESS. When the user tries to select Ok on the corresponding test, they receive the following message:

Example error message for the scenario described on this page.

Users can ignore all open bugs by selecting the Ignore open bugs checkbox.

You can configure JSU’s preconditions in the following ways:

  • Negate the precondition result

  • Combine the result with the result of previous preconditions using the following options:

    • Discard the result of the previous precondition: Results of the previous preconditions are not taken into account

    • AND: All of the preconditions have to be true to execute the post function

    • OR: Only one of the preconditions has to be true to execute the post function

Example of a precondition configuration as described on this page.

Learn more in Workflow preconditions.

  • No labels