Skip to end of banner
Go to start of banner

Fields Required Validator

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 13 Next »

Description

The 'Fields Required' checks whether values for specified fields are set for a given transition. If the check fails, no action will be performed.

Since version 1.4.10, Σ Time Spent may be used to check whether work has already been logged once, before the current transition or within itself. And a new option has been added, to be able to ignore the context check on fields made by the app.

Configuration

You must select mandatory fields, when configuring the transition. For example:

JSU default behaviour is to apply the context settings, this means that a field that is required by this check, but having no valid context for the current issue, wont be checked. Thus you may select 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. 

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

You can define a custom error message for most 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, and make it difficult for your users to understand and resolve the error. 

Example custom error message for a JSU validator that tells users that the due date cannot be later than the resolved date.


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 its value not set, the check will fail and no action will be performed.

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.

  • No labels