Versions Compared

Key

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


Section


Column
width30%600px


Panel
borderColor#333f48
bgColor#FFFFFF
titleColor#eeeeee
borderWidth1
titleBGColor#333f48
borderStylesolid
titleOn this page

Table of Contents
maxLevel1



Column




Example: Set assignee depending on issue type

My immediate question is: How can I set assignee base on issue type? e.g. issue type Bug = 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 = assignee X, issue type Bug + Component B = 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

Image Removed

Image Added


I answer to your second question: you You can make setting of target field dependent on more than one field by setting an auxiliary field  (for example, Ephemeral string 1)  with composition of more than one field, and configure the parameter "Field to be checked for matching with the set of setting rules" with this auxiliary field.

We want to set "Assignee" in create transition with a user based on the value of "Issue type" and "Components":

We use post-function Copy parsed text to a field to set field "Ephemeral string 1" with a composition of fields "Issue type" and "Components", using character '@' as separator:

Image Removed

Text to be parsed is: %{00014}@%{00094}

Note that:

  • %{00014} is virtual field code for "Issue type"
  • %{00094} is virtual field code for "Components"

Image Added


We use post-function Set a field as a function of other fields to write the setting rules we want. In this case we write 4 rules for issue types "Bug" and "New Feature" and components "Component A" and "Component B". We write a 5th rule to cover rest of case (as an "else" in an "if" statement).


Image RemovedImage Added


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 write 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:


Image RemovedImage Added



Other examples of that function

Set a field as a function of other fields

Incoming Links
pageSet a field as a function of other fields
labelsexample



Copy parsed text to a field

Incoming Links
pageCopy parsed text to a field
labelsexample



Related Usage Examples

Content by Label
showSpacefalse
cqllabel = "example" and label = "post-function"