Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Jira automation "Create issue with "more options""

Hi everyones,

Is someone can tell me why this is not working?

I use jira automation to create task.

My problem is when I create more than one issuelinks. this solution works for components. so i know that my syntax is ok. please see the bold character for the part that is not working.

Please help

"fields": {
"Epic Link": "{{#createdIssues.get(4)}}{{key}}{{/}}"
"add": {
"type": {"name": "Blocks"},
"inwardIssue": {"key": "{{#createdIssues.get(8)}}{{key}}{{/}}"}
} },{
"add": {
"type": {"name": "Blocks"},
"inwardIssue": {"key": "{{#createdIssues.get(7)}}{{key}}{{/}}"}
} },{
"add": {
"type": {"name": "Blocks"},
"inwardIssue": {"key": "{{#createdIssues.get(6)}}{{key}}{{/}}"}
} },{
"add": {
"type": {"name": "Blocks"},
"inwardIssue": {"key": "{{#createdIssues.get(5)}}{{key}}{{/}}"}

1 answer

Hi @Benoit 

Would you please post an image of your rule and audit log for context?

What is happening when you say it is not working?  For example, does it show an error, not add the links, or do something unexpected?

Best regards,

no error, it keeps only one link.

I think the Automation is based on the rest API and the rest API does not support more than one link at a time...

Hmmm... Have you tried to add the links one at a time with separate actions?  It appears that you have a known number of issues to link.

Your proposed strategy is possible if I modifying the trigger issue, but the current situation is that I am creating a bunch of Epic and Issues. (kind of a template) So I have multiple dependency for all those different issues created.

Hi Benoit,

Thanks, and I understood that from your JSON snippet.  I noted your use of {{createdIssues}} with specific issues, such as get(8), and so I wondered if you could update the target issue with the links one at a time.  Apologies if I am misunderstanding your use case.



simple answer, it happened in some cases, that from one issue, 4 cannot be started before the first issue is done. Then those 4 issues need to be closed before the next one start.

I can do that manually, but with automation I can't figure it out.

Okay, there could be timing issues.  The pieces of an automation rule can execute asynchronously, which certainly causes some problems.

Would you please post an image if the full rule?  That will help the community see some context for the symptom you are seeing.  Thanks!

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Atlassian Automation

Jira Automation: Sum Up Story Points Roundup (Initiatives -> Epics -> Story/Tasks -> Subtasks)

Hi Everyone, In this roundup we combine all the jira automation rules to sum up story points across different issue types. We start from the lowest level, summing up story points from sub-tasks t...

1,761 views 2 7
Read article

Community Events

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

Events near you