Fields Required Validator

Description

The 'Fields Required' validator checks whether values for specified fields are set for a given transition.

Configuration

You must define which fields should be mandatory fields when configuring the transition. JSU default behavior is to apply the context settings; this means that a field that is required by this check, but has no valid context for the current issue, won't be checked. You can choose to ignore the context, in that case, a field will be required by this check 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 'Fix Version' 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.

For more information on how to configure a check in Jira, see the Jira documentation.

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. This might be a bit too technical, making it difficult for your users to understand or resolve the error. 

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.