Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published by Scroll Versions from this space and version 2.6.2


Section


Column
width600px


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

Table of Contents
maxLevel1



Column




Features used to implement the example



Example: Assign new issues to a different project role depending on field value in current issue

First of all, using groups in a workflow impairs its reusability. It's much better to use project roles. You should use groups only for assigning users to project roles. As you surely know, Jira issues can only be assigned to one single user or to be unassigned.

Jira Workflow Toolbox implements a functionality for setting a default user for a project role per project. Once you have done this using project properties or user properties, you can assign your issues or sub-tasks created by Create issues and subtasks post-function as I explain in the following example.

I explain you how to assign issues according to Priority of current issue (the issue that is executing the post-function). The behavior implemented in the example is:

If Priority or current user is Critical or Blocker assign new issue to project role Managers.
If Priority or current user is Major assign new issue to project role Administrators.
Otherwise assign new issue to project role Developers.


Once configured, you have:



String expression is:

getMatchingValue(%{00017}, ["Blocker", "Critical", "Major"], ["Managers", "Managers", "Administrators", "Developers"])

Note that:
  • %{00017} is field code for Priority


Other examples of that functions

Create issues and sub-tasks

Incoming Links
Incoming Links
pageCreate issues and sub-tasks
labelsexample

Assign to project role

pageAssign to project role
labelsexample




Related Usage Examples

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