Versions Compared

Key

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


Panel

On this page

Table of Contents
maxLevel2
exclude(On this page|Use case).*
stylecircle
typeflat
separatorpipe



UI Text Box
sizemedium
typeinfo

Use case

Within Jira you can use different issue types to classify your issues.

In the following use case we explain how to set the assignee based on the selected issue type.


Configuration

UI Steps


UI Step

Add the Update field based on rules to the desired transition or create a new transition.

UI Text Box
typetip

You can add the post function to the create transition of the workflow so that the issue type gets automatically set/updated every time an issue is created.



UI Step

Source field

Choose Issue type


UI Step

Target field

Choose Assignee


UI Step

Rules

UI Steps


UI Step

First rule

UI Steps


UI Step

Select Text comparison


UI Step

Source field value

Enter the name of the issue type, e.g.

Code Block
linenumberstrue
Task



UI Step

Target field value

Enter the username that should be assigned to the ticket when the specified issuetype was selected:

Code Block
linenumberstrue
agrant


UI Text Box
typeinfo

In this case, the user with username agrant will be set as assignee, if the issue type Task was selected.





UI Step

Second rule

UI Steps


UI Step

Select Text comparison


UI Step

Source field value

Enter the name of the issue type, e.g.

Code Block
linenumberstrue
Story



UI Step

Target field value

Enter the username that should be assigned to the ticket when the specified issue type was selected:

Code Block
linenumberstrue
eparis


UI Text Box
typeinfo

In this case, the user with username eparis will be set as assignee, if the issue type Story was selected.





UI Step


UI Text Box
typeinfo

Proceed with the configuration like shown in the previous steps and adapt the rules according to your needs.






UI Text Box
typenote

The current implementation works just fine, as long as issue types don't get renamed. If for e.g., the issue type Bug is renamed to Error the above configured post function won't work correct anymore.

The following implementation is an alternative that even works after renaming issue types!


UI Expand
titleAlternative implementation using issueType()


UI Text Box
typeinfo

Instead of entering the issue type name itself, we will use the parser function issueType() with the issue type id.


UI Steps


UI Step

Head over to your Jira Administration → Issues → Issue types


UI Step

Hover over the Edit button of the desired issue type and grab the id from the URL.


The URL might be something like:

Code Block
http://your-domain.com/secure/admin/EditIssueType!default.jspa?id=10100


UI Text Box
typeinfo

The id can be found at the end of the URL: id=10100.

If the id of the issue type Task was 10100, the expression would be:

Code Block
linenumberstrue
issueType(10100)




UI Step

Update the above rules like follows:

UI Steps


UI Step

First rule

UI Steps


UI Step

Select Logical expression


UI Step

Expression

Enter the the following expression:

Code Block
linenumberstrue
%{issue.issueType} = issueType(<id>)


UI Text Box
typeinfo

Replace <id> with the actual id of the desired issue type.



UI Step

Target field value

Enter the username that should be assigned to the ticket when the specified issue type was selected:

Code Block
linenumberstrue
agrant


UI Text Box
typeinfo

In this case, the user with username agrant will be set as assignee, if the issue type Task was selected.





UI Step

Second rule

UI Steps


UI Step

Select Logical expression


UI Step

Expression

Enter the following expression:

Code Block
linenumberstrue
%{issue.issueType} = issueType(<id>)


UI Text Box
typeinfo

Replace <id> with the actual id of the desired issue type.



UI Step

Target field value

Enter the username that should be assigned to the ticket when the specified issue type was selected:

Code Block
linenumberstrue
eparis


UI Text Box
typeinfo

In this case, the user with username eparis will be set as assignee, if the issue type Story was selected.










Screenshots

Image Added


Related use cases

Page properties report
firstcolumnUse case
headingsJWT feature, Workflow function, Parser functions, Label
sortByTitle
cqllabel = "use-case-workflow" and ancestor = "32211223"


Excerpt Include
DECADIS:Contact support
DECADIS:Contact support
nopaneltrue


Page properties
hiddentrue


JWT feature

Workflow function

Update field based on rules

Parser functionsissueType()
Label



Page properties
hiddentrue



Status
Tech review

Status
colourGreen
titledone

Style guide

Status
colourGreen
titledone

Status
titletodo
Status
colourYellow
titleReady for review
Status
colourGreen
titledone
Status
colourRed
titleflagged