Date: Fri, 29 Mar 2024 10:12:45 +0100 (CET) Message-ID: <1918650746.524.1711703565767@apps-confluence-5.apps-confluence.apps.svc.cluster.local> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_523_1860368282.1711703565766" ------=_Part_523_1860368282.1711703565766 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
My immediate question is: How can = I set assignee base on issue type? e.g. issue type Bug =3D assignee X. = ;I looked at the post-function= Set a field as a function of other fields, but the "Target field to be set:" list does= not contain Assignee. My not so immediate question is: How can I set assignee base on combinations = of issue type and component? e.g. issue type Bug + Component A =3D assignee= X, issue type Bug + Component B =3D assignee Y.
As you can see in the screenshot, = "Assignee" is= the third option in "Target field to be set" parameter of post-function Set a field as = a function of other fields.
I answer to your second question: = you can make setting of target field dependent on more than one field by&nb= sp;setting an auxiliary field (for example, Ephem= eral string 1) with composition of more than one field<= span style=3D"color: rgb(34,34,34);">, and configure the parameter "= span>Field to be checked for matching with the set of setting rules= " with this auxiliary fiel= d.
We want to set "Assignee" in create transition with a u= ser based on the value of "Issue type" and "Compon= ents":
We use post-function Set a field as a function of othe=
r fields to write t=
he setting rules we want. In this case we write 4 rules for issue types "Bug" and "New Feature" and components "
As in Components field you can set more than = one component at the same time, it is convenient to write rules to specify = precedence of components. For example, if you want "Component A" to have precedence over "Component B", you should w= rite this set of rules:
(Bug@.*Component A.*)feynman
(Bug@Component B)einstein
(New Feature@.*Component A.*)kaku
(New Feature@Component B)newton
(.*)admin
Once configured, transition looks like this:
Set a field as a function of other fields