On this page
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 with a project key corresponding to the email's domain.
Configuration
Project*
Choose Set project manually (parser expression)
Expression*
Set it to advanced text and use the following expression:
toUpperCase(toString(findPattern(%{issue.reporter.email},"(?<=.*@)([a-zA-Z0-9_-]+(?=\\.))")))
This expression grabs the domain from the reporter's email and transforms it to upper case:
| Email address | Return value |
|---|---|
| admin@atlassian.com | ATLASSIAN |
| doe@realcompany.com | REALCOMPANY |
So for every key account there is one dedicated project with the corresponding project key.
Issue type*
Choose Retain the issue type
Status*
Choose Retain the status.
Conditional execution
Enter the following expression
isInGroup(%{issue.reporter}, "key-account")
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.
Related use cases
STAFF PICKUse case JWT feature Workflow function Parser functions Label Move an issue to another issue type 
Move an issue to another project Triage issues created by email
If you still have questions, feel free to refer to our support team.
