Custom field value change required

Overview

The Custom field value change required validator allows you to block a workflow transition if the value of a custom field hasn’t changed since the issue was created.

Configuration

  1. Select a custom field in the Custom field field to be validated against being changed (see Supported fields below)

  2. Define the text of the error message in the Error message text field (e.g. “Field Text hasn’t been changed”)

  3. Activate the JQL condition option and define the JQL query that has to be met by the issue in order for the validation to work (e.g. “type = Bug and Priority = Blocker”)

  4. Activate the Executor condition option if you want the validator to work only if the user is or isn’t in a certain Jira user group or project role

    1. Select if The executor has to be or can’t be a member of a certain Jira user group or project role

      1. Select a Jira user group in the Group field if Group was set in the member of a field

      2. Select a project role in the Project role field if Project role was set in the member of a field

Supported fields

The validator supports all custom fields available in Jira by default. Fields provided by external apps are not supported.

Use cases

  • A transition is available when the release date or service date changes