Excerpt Include Universal user-based condition Universal user-based condition nopanel true
The user property value condition allows Jira workflow developers to compare user property value with a fixed value or field value. This powerful mechanism lets you join user properties with the ability to execute workflow transitions. It works perfectly with Set user property value post function and Set issue field from user property value post function.
Using this condition you can do the following:
- Allow the Reporter's manager to execute a transition.
- Transition an issue only if the current user is in the same department as listed in the issue field.
- Transition an issue only if the reporter's grade meets the given criteria.
|Version compatibility||6.0.1 - Latest|
|Introduced in version||1.0.0|
A list of user fields to check the property against one of them. They are:
|Reporter||A person who entered (directly or indirectly) the issue into Jira. It can be different than the issue's creator.|
|Creator||A person who physically created an issue in Jira. In most cases, it's equal to Reporter. (available in Jira 6.2 and newer).|
|Assignee||A person to whom the issue is currently assigned.|
|Current User||The currently logged-in user.|
|Other Field||A user is shown in any user type custom field.|
User Property key
The name (key) of the property to be checked.
Source of value
It's a method of comparison. There are two options available:
Fixed value - compares user property value to a given fixed value.
Field value - compares user property value to the value from a selected issue field.
Select field/Fixed value
It's an option to provide the expected issue field or the fixed text value. If the property value is the same as field/fixed value, the condition passes, otherwise, it fails.
If user property does NOT exist
Condition behavior when the property value cannot be found for a given user.