View Source

Use case

Jira can be perfectly used to communicate with your customers, e.g. by using Service Desks 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.

Choose Set project manually (parser expression)

Set it to advanced text and use the following expression:

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

Choose Retain the issue type

Choose Retain the status.

Expression

set it to logical and use the following expression

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.

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

otherwise, you would get this warning message

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

JWT feature
Workflow function	Move issue
Use case description	Sort issues created by email automatically.
Label