Versions Compared

Key

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

If you’ve configured your instance to create issues through email requests, you can refer to this article explains to learn how to automatically assign newly created issues (through email requests) to a specific user - . We will assign issues, based on the keywords in the email subject/email body - using the Update Any Issue Field (JSU) post - function.

Info

Use cases:

Instructions

Example use casescenario: If the email has 'Dev' or 'QA' in the subject, the ticket needs to be assigned to user1. If it has 'Deploy' or 'Prod', it needs to go to user2.

  1. Login Log in as a Jira Admin and edit go to the workflow that is associated with your project and issue type.

  2. In the workflow, click Edit to switch to Edit mode.

  3. Select the Create transition and , then select the Post Functions tab and click Add post function.

  4. Select “Update the Update Any Issue Field (JSU) post - function and then click Add.

  5. In this, add Add two Regular Expression pre-conditions: One for Dev and another for QA, and then add the below following regular expressions:
    For Dev :

    Code Block
    ^[\s\S]*Dev[\s\S]*$

    For QA

    Code Block
    ^[\s\S]*QA[\s\S]*$
  6. Select "OR" in the pre-condition section and select “True” True under “Preconditions must be”.

  7. Select the Assignee field and add the account id ID of user1 in the Field Value. Refer to the screenshot as illustrated below:

    Image RemovedImage Added
  8. Click “Add” Add.

  9. Similarly, add another Update Any Issue Field (JSU) post - function on the Create transition for 'Deploy', 'Prod' and add the account id ID of user2 in the Field Value and publish the .

  10. Publish your workflow.

  11. If you want to verify the email body instead of the subject, then replace Summary with Description in the Regular Expression pre-conditions.

  12. Place these post - functions below “Creates Creates the issue originally.” built-in post - function on the create Create transition.

Info

It is recommended to test this scenario in a non-production environment, before environment before implementing it in a production environment.