Automation to link issues to another issue

[Pradheep Ayyanar]

I have few issues (sub-task) that needs to be linked as "Blocked by" to one of the issue in the same story.

Ex:

I have this task "MDU-13347" and this can be started only when "MDU-10466" is completed. I need to do automation to link this issue as blocked by as i have multiple scenarios like this and also projects. 

@Trudy Claspill can you help here

[Trudy Claspill · Accepted solution]

Hello @Pradheep Ayyanar 

I want to first speak to you mentioning me by name, asking for my help, only 11 minutes after having posted your question.

Please note that I am saying this from a place of kindness, and I very sincerely encourage you to keep participating in this community and asking your questions.

I recommend that you allow more time, at least several hours and perhaps even an entire business day, for other community members to see and respond to new questions before attempting to elicit an answer from a specific community member. Speaking only for myself, I have a full time job that does not include participating in this community. I contribute to this community when I can and when it doesn't interfere with my work responsibilities.

Calling out a specific community member does not mean that community member is available to respond to your question. And for people scrolling through the pages of questions, some may even skip over your question assuming that the response count indicates other community members have already responded.

Setting that aside, let us now consider your question.

This seems very similar to the other question you posted on Sept. 19, where I provided suggestions.

https://community.atlassian.com/t5/Jira-questions/Automation-based-on-the-summary-text-and-status/qaq-p/2816489

I have the same question for you here as I had then:

- How do you identify the issue to which you want to link the newly created issue? Is that again based on the Summary text, like in you previous question?

If so, then the solution may be almost identical.

When an issue is transitioned to Complete Created
And that issue is a Sub-task
And the Summary of that issue is {the text you provided}
Then find all sibling subtasks that have the Summary {the text of the sibling issue summary}
And transition those subtasks to In Progress link each of those issues to the trigger issue

Trigger: Issue Created
Condition: Issue Fields Condition
  Field: Issue Type
  condition: equals
  Value Sub-task
Condition: Issue Fields Condition
  Field: Summary
  condition: equals
  Value: {the text you supplied}}
Branch: Related Issues: JQL
  JQL: parent={{issue.parent.key}} and Summary ~"\"{the text you supplied}\""

    Action: Link Issue

You may find it valuable to spend some time reviewing the documentation for Automation. There is a lot of information about conditions and actions and branching available in that documentation.

https://support.atlassian.com/cloud-automation/docs/jira-cloud-automation/

There is also free training available from the Atlassian University.

https://university.atlassian.com/student/catalog/list?search=jira+automation

[Pradheep Ayyanar]

Thank you so much and understood on your first point clearly. I will ensure to not mention henceforth.

Thanks for the references and notes. let me take a quick look to see if the issues are linked.

[Pradheep Ayyanar]

It worked and thanks much. 

[Pradheep Ayyanar]

@Trudy Claspill can you help here