Value Field Precondition

Description

The 'Value Field' condition compares the current value of a field against a predefined value. It can compare strings, numbers, or option IDs. For select fields, you can compare either by string or option ID. The ID may be preferable since the name, or string, of an option may change over time, the ID does not. If a field can have several values (like components), matching one value is sufficient to pass the check.

Configuration

You must specify the field and value that will be the prerequisite for the check.

If you choose the comparison type String, only '=' and '!='are valid options. 
You can leave the value empty and choose comparison type '!=', to specificy that a given field is required for the condition. 
For date fields without time, use the format 'yyyy-MM-dd' for values, and for those with time 'yyyy-MM-dd HH:mm'. 
For example, February 12th 2014: 2014-02-12, at 8:05 AM: 2014-02-12 08:05, at 4 PM: 2014-02-12 16:00.

Example

A workflow is configured so that the 'Start Progress' transition has the 'Value Field' condition set to 'MultiSelect' = '10021' (option ID). A user viewing an issue in that workflow will not see the 'Start Progress' transition unless 'MultiSelect' has at least the option with ID '10021' chosen.

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.