Introduction
Complex element
This workflow element is complex and may be a little confusing for beginners. In case of any questions please contact us via our Service Desk.
It operates on all JIRA standard and custom fields including reporter, creator (since JIRA 6.2), assignee, project lead, etc.
For example you can build following conditions using our solution:
- Only/except Current Assignee can execute a transition
- Transition can be executed by any user but one previously executed transition from Open to In progress status
- Transition can be executed only if Project lead has "Schedule issue" permission
| Element summary | |
|---|---|
| Status | CURRENT |
| Version compatibility | 6.0.1 - Latest |
| Supported | Yes |
| Introduced in version | 1.0.0 |
Condition parameters
First (upper) list
First list contains a number of options (subject). Most of them are connected to current issue such as Issue's reporter, assignee, etc. They are:
| Option | Description |
|---|---|
| Reporter | The person who entered (directly or indirectly) the issue into JIRA. It can be different than issue's creator. |
| Creator | The person who physically created an issue in JIRA. In most cases it's equal to Reporter. (available in JIRA 6.2 and newer) |
| Assignee | The person to whom the issue is currently assigned. |
| Current User | Currently logged in user. |
| Project Lead | User fulfilling the role of project leader for current project. |
| Specific user | Any username(s) to be entered manually. |
| Other Field | The person shown in any user type custom field. |
Second (lower) list
Second list contains a number of conditions to be evaluated against the persons from the upper list.
| Option | Description |
|---|---|
| In Groups | Checks if a person is in all/any JIRA groups. |
| In a Group field | Checks if a person is in groups determined by a custom field. |
| Has roles | Checks if a person is in project roles in project the current issue belongs to. |
| Has roles(s) from a field | Checks if a person is in roles determined by a custom field. |
| Has permissions | Checks if a person has specific permissions granted for current issue. |
| Is also in field | Compares a person from an upper list with any other user type field in JIRA. |
| Executed transition from status | User selected from an upper list executed (whenever for current issue) a transition from/to status |
| Is specific user | Any username(s) to be entered manually. |
For most options listed above you can choose between "All" or "Any" options.
Condition result inversion
Most of the Workflow PowerBox conditions including this one allow conditions inversion. If you tick "Inverse condition" option, checking result will be inversed. It allows you to create a set of "except" conditions such as:
- all users except issue reporter can execute a transition
- execute transition only if current assignee is not in jira-administrators group
- etc.
Remember that if you use an external condition that does not support result inversion you can still inverse it using Condition Templates as described on Condition templates page.
