You must have the Jira System Administrators global permission before you can carry out the instructions on this page. |
The Conditional Rules Administration screen looks like as follows:
The Conditional Rules Administration screen allows you to add, edit, delete and review your Conditional Rule configurations.
Furthermore, when moving the mouse upon the data under the Assigned Approval, Assigned Template, Assigned Mapping, Assigned Issues columns , a window, detailing when the Conditional Rule is applied, shows up.
Before you can create Conditional Rules, you must set up Conditional Rule Main Settings.
On the Conditional Rule Settings screen, you must select the user that the app will use to evaluate the Conditional rule .
On selecting a different user, the app grants the permissions to the new user and revokes the permissions to the previous user accordingly. |
By default, the app grants browsing permissions on all Jira Projects to the selected user.
You can choose to disable this automatism by turning Off the Grant Browsing Permissions Automatically option.
Click Add Conditional Rule to create a new Conditional Rule
choose the option Super User, if you want that the Conditional Rule is evaluated via the credential of the user selected on the Conditional Rule Main Settings (Default)
choose the option Current User, if you want that the Conditional Rule is evaluated via the logged user credentials
select a single user picker custom field, if you want that the Conditional Rule is evaluated via the user selected on the selected user picker Custom Field.
You can choose only one of the options listed above. |
If the selected User used to evaluate the conditional rule is null (e.g. reporter= Anonymous, assignee=Unassigned, current user =null, user selected on the user picker Custom Field=null) the condition will return false. |
You are able to update an existing Conditional Rule.
The majority of the filled fields can be updated, exception made for the Rule Name.
When deleting a Conditional Rule not yet associated to any Approval, Approval Mapping, Single Issue Approval configuration or email Template, the application doesn't ask to confirm.
If any configuration, requiring the Conditional Rule, exists, the application asks to confirm the deletion of the Conditional Rule.
Conditional Rule validity is based on the following variables:
This section illustrates which changes have impact on Conditional Rule validity and how you can fix them.
Notice that when a conditional rule is retrieved invalid the condition is assumed as not set and the user is alerted as showed on the following screenshot:
In order to evaluate a Conditional Rule via the credential of the user selected on the Conditional Rule Main Settings, the selected user needs Browsing permission on the Project using the Conditional Rule.
Changes having impact on user validity and the correct way to restore Conditional rule validity are listed below:
user is deactivated
Upgrade the Conditional Rule Main Settings by selecting a different user. |
username is updated
When updating the selected user, the app automatically grants the selected user of the Browsing permission on all Projects. |
user is deleted
Upgrade the Conditional Rule Main Settings by selecting a different user. |
user has no Browsing permission on a new Permission Schema
You have two options: manually grants the user of the Browsing permission or just navigates the Conditional Rule Main Settings and click Save. |
The Conditional rule expression expects a query using the Jira Query Language (JQL) sintax.
When creating or updating a Conditional rule expression the JQL check button confirms the validity of the expression.
You are able to save valid Conditional Rules exclusively.