Get started

Use case library

JWT expression editor

JWT expression parser functions

JWT workflow functions

JWT remote actions

JWT automation rules

JWT calculated fields

JWT calendars

JWT properties

JWT JQL functions

Cloud migration hub

Additional product info

Versions Compared

Old Version 15

changes.mady.by.user Jona Ittermann

Saved on

compared with

New Version Current

changes.mady.by.user Iheb Kharab

Saved on

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

Jira can be perfectly used to communicate with your customers, e.g. by using Service Desks Management or dedicated projects.

It is also possible to create issues via email. But in this case the created issues always belong one specific project.

In the following use case, emails sent by one of our key account customers will be automatically moved to the corresponding project.

Every key account customer is part of the group key-account and every key account company has one dedicated project within Jira with a project key corresponding to the email's domain.


Image Added


UI Text Box
typewarning

Make sure this post function is the last one on your post functions list.



Configuration

UI Steps


UI Step

Add the Move issue post function to desired workflow transition.


UI Step

Project

Project*

Choose Set project manually (parser expression)


UI Step

Expression

*

Set it to advanced text and use the following expression:

Code Block
linenumberstrue
toUpperCase(toString(findPattern(%{issue.reporter.email},"(?<=.*@)([a-zA-Z0-9_-]+(?=\\.))")))


UI Text Box
typeinfo

This expression grabs the domain from the reporter's email address and transforms it to upper case:

Email addressReturn value
admin@atlassian.comATLASSIAN
doe@realcompany.comREALCOMPANY

So for every key account there must be one dedicated project with the corresponding project key.

The used expressions are



UI Step

Issue type

*

Choose Retain the issue type


UI Step

Status

*

Choose Retain the status.


UI Step

Conditional execution

Expression

set it to logical and use Enter the following expression

Code Block
linenumberstrue
isInGroup("key-account", %{issue.reporter})

After checking if the parameters match this example, you can click on add and this is how the post function should look like.

Image Removed

, "key-account")


UI Text Box
type
warning

Make sure this post function is the last one on your post functions list.

info

By using the conditional execution, the created issue will only be moved to the correct project, if the reporter is a key-account customer.

The used expression is isInGroup().





Image AddedScreenshots

Image Added

otherwise, you would get this warning message

Image Removed

Now that you are familiar with this post function and what it does, you can configure the parameters based on your needs.


Image ModifiedRelated use cases

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

Excerpt Include
DECADIS:Contact support
DECADIS:Contact support
nopaneltrue


Page properties
hiddentrue


JWT feature

Image Modified

Workflow function

Move issue

Use case descriptionSort issues created by email automatically.
Label
Parser functions

toUpperCase() 

toString() 

findPattern() 

isInGroup()

Label

Status
colourRed
titleSTAFF PICK



Page properties
hiddentrue



Status
Tech review

Status
colourGreen
titletododone

Style guide

Status
colourGreen
titletododone

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


...