Date: Fri, 29 Mar 2024 14:37:52 +0100 (CET) Message-ID: <931793833.588.1711719472532@apps-confluence-5.apps-confluence.apps.svc.cluster.local> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_587_1920681424.1711719472532" ------=_Part_587_1920681424.1711719472532 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
First of all, using groups in a workflow impairs its reusability. It's m= uch better to use project roles. You should use group= s only for assigning users to project roles. As you surely know, Jira issue= s can only be assigned to one single user or to = be unassigned.
Jira Workflow Toolbox implem=
ents a functionality for setting a default user for a project role per project<=
/a>. Once you have done this using project properties or
I explain you how to assign issues according to Priority of current issue (the issue that is executing the post-f= unction). The behavior implemented in the example is:
If Priority or current user is C=
ritical or Blocker assign new issu=
e to project role Managers.
If Priority or current user is Maj=
or assign new issue to project role Administrato=
rs.
Otherwise assign new issue to project role Developers.
Once configured, you have:<= /p>
String expression is:
getMatchingValue(%{00017}, = ["Blocker", "Critical", "Major"], ["Managers", "Manager= s", "Administrators", "Developers"])