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; } } }

Link issues from different projects based on parent issue summary

Krzysztof Kiser

Hi,

I need help with setting up an automation rule.
I have two projects in which every month, there is a new Story created with the name of the month and a year (e.g. August 2020).
In one of the projects in addition to the Story, there are certain sub-tasks created.

My requirement is to link those sub-tasks to the issue created in another project based on the sumamry of the sub-tasks parent.
If a sub-task parent summary = summary of an issue in the other project then link. Otherwise do nothing.

Here's an example of what I need to do:

Project 1 (all auto-created using automation every month)
Story: August 2020 [under epic ABC-1]
Sub-task 1: To do [parent summary: August 2020]
Sub-task 2: To approve [parent summary: August 2020]
Sub-task 3: To resolve [parent summary: August 2020]

Project 2: (story auto-created using automation every month)
Story: August 2020 [under epic BAA-7]

I need to create "relates to" links for all those sub-tasks from project 1 where parent summary = summary of story from project 2.

Is this something I'd be able to do with any of the automation apps?

I already have a custom field that returns a parent name for all issues, so I only would need to compare the custom field in the two projects and link issues based on that.

What would be the best way to accomplish this?

Accepted answers

Florian_8erf7n

Hi @Krzysztof Kiser I did it in our playground (german Spielwiese) project and it works fine:

All comments

Florian_8erf7n

Create a rule that is triggered when a subtask is created.

Use a branch rule with JQL “project = other-project-name and summary = {{issue.parent.summary}}”

Set a link between this {{issue.key}} and {{triggerissue.key}} within the branch rule.

Krzysztof Kiser

@Florian I have tried that before, but I think JQL does not accept variables. It gives back an error.

Here's my setup, maybe I've done something wrong.

Screen Shot 2020-08-25 at 11.05.06 PM.png

Screen Shot 2020-08-25 at 11.04.41 PM.png

And here's the error:

Screen Shot 2020-08-25 at 11.05.22 PM.png

Florian_8erf7n

Well it looks good. I will try this tomorrow when I am back in office.

Florian_8erf7n

Hi @Krzysztof Kiser I did it in our playground (german Spielwiese) project and it works fine:

Florian_8erf7n

The equals comparator (=) is not allowed with the issue field. Use tilde (~) instead and use quotation marks around the smart value.

Krzysztof Kiser

@Florian thanks for this, but your setup only comments on the issues. I need to link them, not comment.

Actually, after thinking about this, I don't think what I want to achieve is possible.
Issues in both projects are auto-created at the same time, so I don't see an option to implement the linking within Automation for Jira and the scheduled automation to link them.

This is a bit complicated. I guess, I will just be linking the issues on a monthly basis.

Thanks for the effort to help though. I appreciate it.

Florian_8erf7n

Well I did the comment to prove the concept. Linking should work the same way.

You say „at the same time“. That is something I highly doubt.

When you use a single automation rule the create both issues then you can create the „collector“ issue first and add a delay of some seconds to be sure it is finished before you create the „parent“ issue. Afterwards you can create all the sub issues to your parent.

Let me check the linking stuff for you. I will write again...

Welcome!

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

Quick Links

Find more posts tagged with

server

custom-field

jira-software

jira-software-server

issue-link

epic

link

automation

sub-task

story