Hello all, I have the following use case: * I periodically receive structured emails from a third party. * I have configured JIRA to create an issue for each email received (Epic). * After the issue is created, a rule is triggered to "process" the issue --> the main objective is to extract from the email body (stored in the issue description field), the values of different custom fields. This works like a charm. Now I am trying to go further, and I would like to, based on the value of one of the issue custom fields, to be able to create an issue relationship between the recently created issue (Epic), and a third issue (custom issue type). Is this possible?

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Automation rule after creating an issue

Javier Cárdaba

Hello all,

I have the following use case:

I periodically receive structured emails from a third party.
I have configured JIRA to create an issue for each email received (Epic).
After the issue is created, a rule is triggered to "process" the issue --> the main objective is to extract from the email body (stored in the issue description field), the values of different custom fields.

This works like a charm. Now I am trying to go further, and I would like to, based on the value of one of the issue custom fields, to be able to create an issue relationship between the recently created issue (Epic), and a third issue (custom issue type).

Is this possible?

Accepted answers

Muhammad Ramzan_Atlassian Certified Master_

Welcome to Atlassian community. If I understood correctly, you want to create two more issues based on custom field values and associate them with epic.

Yes , it is possible, please have a look at attached screenshot. Please feel free to reply back if my assumption is wrong so can help you in better way.

All comments

Muhammad Ramzan_Atlassian Certified Master_

Welcome to Atlassian community. If I understood correctly, you want to create two more issues based on custom field values and associate them with epic.

Yes , it is possible, please have a look at attached screenshot. Please feel free to reply back if my assumption is wrong so can help you in better way.

Daniel Ebers

Hi @Javier Cárdaba

adding to the great visualization of Muhammad I wanted to add a link to an Automation video which could be of help:

How to create linked issues automatically upon issue creation in Jira
https://www.youtube.com/watch?v=4cIVNl2-oao

From what I seem to have understood you also want to link the issue as soon as created.

Could you please check it is what you meant and let us know if you succeeded?
If not, please share what you have.

Regards,
Daniel

Darryl Lee

I think the only problem is here:

After the issue is created, a rule is triggered to "process" the issue --> the main objective is to extract from the email body (stored in the issue description field), the values of different custom fields.

So the trigger is create, and then he'll need to Edit fields based on match values.

I'm worried that the because Automation actions can fire asynchronously, that any check for a field value may happen before the field is set by the Edit action. (Even if it is laid out in the proper order.)

BUT. I think there's a solution. You set up that first rule above to parse and edit the custom fields upon issue creation.

Then you would set up a second rule whose trigger is: "Field value changed", and have it trigger when the field is Changed. And then (this is the important part), you need to Allow rule trigger:

Check to allow other rule actions to trigger this rule. Only enable this if you need this rule to execute in response to another rule.

This will allow the edits to happen, and THEN, when the fields are set, that will trigger the second rule, where you can create the related issues (or link them, whatever.)

Javier Cárdaba

Dear Muhammad, thank you for your reply. Your assumption is not correct (and that's because I haven't explained properly). Let me try again:

The issues that I want to relate through creating the relationship already exists, and therefore, no issue need to be created.
Issue 1 (Epic) has a custom field X with value "A".
Issue 2 (custom issue type) has a custom field Y with value A.
Issue 1 (Epic) is the one triggering the automation rule. I this workflow, based on the content of the custom field X I need to locate the issue 2 (using JQL to target the custom field Y.
For each issue found, new relationship needs to be created.

Does it make more sense now?

Thanks

Muhammad Ramzan_Atlassian Certified Master_

I see, now its clear to me. Thanks for the clarification.

So you can't achieve it by above way. Here is new way. Please have a look at attached screenshot.

What I did, I saved the triggering issue(epic) value in a variable and used that value to execute the JQL then linked the resulting issues with the triggered issue.

Hope it will be helpful.

Javier Cárdaba

Dear Muhammad,

I have arrived to the solution you have summarized in your feedback, so... THANK YOU!

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud

automation