Skip to end of banner
Go to start of banner

Fields Required Precondition

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 »

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 Fields Required validator checks whether values for specified fields are set for a given transition.

Configuration

Define which fields should be mandatory for the transition. JSU’s default behavior is to apply the context settings; this means that if a field is required by this check, but has no valid context for the current issue, it won't be checked. You can choose to ignore the context, in that case, a field will be required even if its context is not configured for the current issue. 

Example

A workflow is configured so that the Resolve transition has the Fields Required check where the Fix Version field is mandatory. If a user attempts to resolve an issue on this workflow, where the Fix Version field value is not set, the check will fail and no action will be performed.

Example configuration of the Fields Required validator as described on this page.

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.

Supported field types

JSU supports many different field types such as system fields and custom fields. However you should be aware, that not all field types are supported, and not in all combinations. We aim to cover the most important field types and are continuously adding and improving how different field types are supported. Some custom fields of other third-party apps might never be supported. You should always test anything you do with issue fields with JSU. You can try it with a free 30-day evaluation license.

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