I have the following use case:
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?
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.
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:
Does it make more sense now?
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.
adding to the great visualization of Muhammad I wanted to add a link to an Automation video which could be of help:
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.
I think the only problem is here:
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.)
Hey there Cloud Community members! We’re excited to give you the first glimpse of the new home for business teams on Jira — Jira Work Management. Jira Work Management is the next generation of J...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events