Introduction
| Excerpt | |||||
|---|---|---|---|---|---|
|
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 the following conditions using our solution:
- Only/except Current Assignee can execute a transition.
- Transition The transition can be executed by any user but one previously executed transition from Open to In progress status.
- Transition The transition can be executed only if the Project lead has the "Schedule issue" permission.
| Element summary | |||||||
|---|---|---|---|---|---|---|---|
| Status |
| ||||||
| Version compatibility | 6.0.1 - Latest | ||||||
| Supported | Yes | ||||||
| Introduced in version | 1.0.0 | ||||||
Condition parameters
First The first (upper) list
First The first list contains a number of options (subject). Most of them are connected to the current issue such as the Issue's reporter, the assignee, etc. They are:
| Option | Description |
|---|---|
| Reporter | The person who entered (directly or indirectly) the issue into JIRA. It can be different than the issue's creator. |
| Creator | The person who physically created an issue in JIRA. In most cases it's equal to the Reporter. (available in JIRA 6.2 and newer). |
| Assignee | The person to whom the issue is currently assigned. |
| Current User |
| The currently logged in user. |
| Project Lead |
| The user fulfilling the role of the 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 The second (lower) list
SecoThe 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 the 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 |
| The user selected from an upper list executed (whenever for the current issue) a transition from/to a status. | |
| Is specific user | Any username(s) to be entered manually. |
For the most of the 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 the "Inverse condition" option, the checking result will be inversed. It allows you to create a set of "except" conditions such as:
- all users except the issue reporter can execute a transition,
- execute transition only if the current assignee is not in the jira-administrators group,
- etcother.
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 the Condition templates page.
