Workflow PowerBox for JIRA
Page tree

Versions Compared

Old Version 2

changes.mady.by.user Unknown User (aleksandra.luszowska@infodesign.pl)

Saved on

compared with

New Version Current

changes.mady.by.user Nadiia Lisovska

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Introduction

Complex element

This workflow element is complex and

may be

maybe a little confusing for beginners. If you have any further questions, please contact us via our

Service Desk

 Customer Portal.

Excerpt
Info
title
Universal


A universal user-based condition is a powerful tool that allows you to check most of the user relations in an issue.

It operates on all JIRA Jira standard and custom fields including the reporter, creator (since JIRA 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
Status
colourGreen
titleCurrent
Version compatibility6.0.1 - Latest
SupportedYes
Introduced in version1.0.0


Condition parameters 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:

OptionDescription
Reporter
The
A person who entered (directly or indirectly) the issue into
JIRA
Jira. It can be different than the issue's creator.
Creator
The
A person who physically created an issue in
JIRA
Jira. In most cases, it's equal to the Reporter. (available in
JIRA
Jira 6.2 and newer).
Assignee
The
A person to whom the issue is currently assigned.
Current User
Currently
The currently logged-in user.
Project Lead
User
A user fulfilling the role of the project leader for the current project.
Specific userAny username(s) to be entered manually.
Other Field
The
A person is 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.
 

OptionDescription
In GroupsChecks if a person is in all/any
JIRA
Jira groups.
In a Group fieldChecks if a person is in groups determined by a custom field.
Has rolesChecks if a person is in project roles
in
of the project which the current issue belongs to.
Has roles(s) from a fieldChecks if a person is in roles determined by a custom field.
Has permissionsChecks if a person has specific permissions granted for the current issue.
Is also in the fieldCompares a person from an upper list with any other user type field in
JIRA
Jira.
Executed
The executed transition from status
User
A user selected from
an
the upper list executed (whenever for the current issue) a transition from/to a status.
Is a specific userAny username(s) to be entered manually.

For 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 inversedinverted. It allows you to create a set of "except" conditions such as:

  • all users except the issue reporter Reporter can execute a transition,
  • execute transition only if the current assignee Assignee is not in jirathe 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.