Value Field Precondition

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


The Value Field precondition checks whether a field on the issue matches a value.

For more complex scenarios or to combine several Value Field preconditions, you could use a JQL precondition.


You must specify the field you want to check, the operation you want to perform, and the value you want to check against – although you can also check against an empty value.

If a field can have multiple values (e. g., components), the precondition matches if one of the values is contained – or if it is not contained.

The following matching rules apply:

  • Text fields with operators =  or != will match with any text string.

  • Text fields with operators >=, >, <, and <= will match with any number.

  • Number fields will match with other numbers.

  • Date fields will match with other date fields.

  • Date time fields will match with other date time fields.

  • Estimate fields (original, remaining estimate) will match with duration formatted strings like 1w 2d 3h 4m 5s. If no unit is given, minutes are assumed.

  • User fields can be matched against the user name or the account ID.

  • Sprints, select options, components, versions, issue types, priorities, resolutions, security levels, and statuses are matched against their name or ID.

  • Projects are matched against their name, key, or ID.


An Update Any Issue Field post function is added to the Create transition. A new comment should be created when the number of story points is exceeded, telling the user to break up the story.

Summary of the Update Any Issue Field post function as described on this page.
Example of the Value Field preconditions set up for Original Estimate, Story Points, and Issue Type.

Supported fields types