JIRA AUTOMATION - Story adding into an Epic

[Mane Zakaryan]

Hello everyone.

Can someone help me please. I don't understand what am I doing wrong that my conditions are not working.

I automated the tasks creations, as you see on the capture FIRST I have an Epic creation (it is creating correctly with all correct detailed information including Epic name)

Then I have a STORY creation, which is creating correctly.

The only problem is that I want that my created STORY were automatically added in the EPIC. But it is not working.

Can someone Help ?

Also, in the THIRD place I have a sub task for the Story, but The sub task is not creating at all.

What did I miss in my configurations ?

Thank you

[Mane Zakaryan · Accepted solution]

@Bill Sheboy 

I am so sorry, but I have another question, maybe you can help me with this too ?

On my automation tree, in the end I have a TASK CREATION (it is working correctly).

This last task I am linking with an EPIC (this is an epic that exists in my Jira projects and this linking is working perfectly)

At the same time, I want that this last created taks were related to the EPIC of my automation tree.

So I have created a condition ''Pour Dernière demande créée'' (last created issue) to modify the fields ''Relates to'', but after that I don't know what intelligent value to put so I will have the Issue Key of my Epic that has been automatically created a little above.

[Bill Sheboy]

Hi @Mane Zakaryan 

Sorry I missed seeing your posts yesterday.  Would you please confirm if your questions are answer or if something is still open?  I ask because both of the threads are marked as "answer accepted" and I saw a note that you had resolved the issues.

Thanks!

[Mane Zakaryan]

@Bill Sheboy 

Hi again,

Yes please, can you check my last question about to linking the separate task (which is complitely in other Epic) to my epic.

Thank you in advance.

[Bill Sheboy]

If you have no branches in your rule, you can rely upon the order issues are created.  And then you can reference the {{createdIssues}} smart value to get() the correct one.  Note this smart value is plural, as it refers to all issues created up to that point in the rule. 

The get() function is a zero-based list, and so the first item index is 0, the next is 1, and so forth.  Let's assume the Epic was the second issue created in the rule, and so its key would be:

{{createdIssues.get(1).key}}

If that does not work, we can try another approach: if only one epic is added during the rule, you can find its key using smart value, list filtering:

{{#createdIssues}}{{#if(equals(issueType.name,"Epic"))}}{{key}}{{/}}{{/}}

That expression will filter the created issues to find the epic, and return the key.

[Mane Zakaryan]

The function get() worked, thank you very much.

You helped me a lot.

[Bill Sheboy]

Awesome; I am glad to learn that helped!

[Bill Sheboy · Accepted solution]

Hi @Mane Zakaryan 

Regarding linking the Story to the Epic, you could enter this smart value into the Epic Link field in the issue create action, rather than using the advanced edit with JSON:

{{createdIssue.key}}

That will refer to the epic created earlier.

Regarding adding the subtask to the story, it appears you are using the correct branch to the most recently created issue first.  What do you see in the audit log details after the rule runs?  Are there any errors shown?

Kind regards,
Bill

[Mane Zakaryan]

Thank you very much, it is working, my story is attached to the EPIC. :) 

About the sub task, I don't understand, because I don't have any error in my logs

It just doesn't create my sub task.

[Bill Sheboy]

Would you please post images of your complete rule and the audit log details showing the rule execution?  Those may help to explain why the subtask is not added.

It is possible this is a timing problem, where the story is not saved fast enough for the rule to use it in the branch.  A way to check that is after the action to create the story, add a Re-fetch Issue action.  That will slow down the rule by about a second and reload the trigger issue before proceeding.

[Mane Zakaryan]

Yes of cours

Capture 1, until storry it is working correctly then I have subtasks,

[Mane Zakaryan]

In the end I have another taks (it is not subtaks, just a separated task creation) and it is working also correctly.

[Mane Zakaryan]

Unfortunately, the Re-fetch action didn't help.

[Mane Zakaryan]

Ah, I got it :)

In fact, my problem was that I created this automation rule for the initial project (project of triggering).

I changed the rule and I make it GLOBAL, and now it has created my sub task.