I'm struggling to be able to link all tickets with the same fix version to a specific issue type

[Stephen Nwadinobi]

My issue is two fold:

- I have bug tickets which have affects versions and not fix versions at times, I just found out the release panel only shows tickets with a fix version, so I need a way to show ALL the tickets with a specific version, whether affected version or fix version in the linked issues section of the "Release" issue type but can't seem to be able to find the right Jira automation rule to do this.

Ideally, all tickets with the same version will be linked to the release ticket as soon as the issue is edited with that version.

We also have multiple code repos (component in Jira), so also thinking to do add a condition where any ticket that adds an unreleased version (fix or affects version) if the code repo is selected then it automatically adds all the tickets to the Not closed status for "release" issue types with that same component.

- I was trying to automate this longer term and actually have something that also checks for bugs with affects versions that are affecting Production versions and automatically being able to edit the issue to set the custom field we have, "Affects production" to Yes.

I will attach the drafts of the automations I attempted.

[Mykenna Cepek]

Hi @Stephen Nwadinobi and welcome to the Atlassian Community.

I'm only going to focus on your first issue (see my P.S. below).

First off, I'm not aware of a "Release" issue type in Jira. It's not clear to me if you've customized Jira to literally create a new issue type called "Release", or if you are confused about how Releases/Versions/FixVersions work in Jira. So you'll have to clarify that for us to help here.

Finding all issues with a certain Release in the "Fix Version" or "Affects Version" fields is simple JQL. I'm going to assume you can handle that, if not, let us know and we can start there.

Working through "Linked Issues" in Jira looking for specific things is a challenge (both in JQL and in Jira Automation). Jira OOB (out-of-the-box, with no add-ons) doesn't support that very well, and there are some things you literally will not be able to do. It would help to know if you have any add-ons which extend your JQL to help with those more advanced use cases.

I hope you can see that without more information, it will be pretty difficult for us to help you with this. I'm only an occasional contributor here, so don't rely on my. I'm trying to help your question get better so that other smart folks here in the community can assist you too.

P.S. It's super helpful here in the Community forum to focus on one problem at a time (such as your first two paragraphs). Once that's handled, then feel free to ask another question to take your efforts further (such as your third paragraph, and then later yet another question for your fourth paragraph topic).

[Stephen Nwadinobi]

Thanks @Mykenna Cepek I appreciate your response.

You are correct, a few things I wrote aren't clear. So yes, a "Release" issue type is a custom field created to capture Software releases on my instance, as it matched our use case.

Using the standard field "Fix version" in a JQL is pretty straight forward as you said, however, adding an automation that allows all Jira issues with the same "fix version" and "component" to be linked to a specific "Release" with a matching "Component" is where I'm stuck.

E.g.

Issue 1 (task) has "fix version" = v0.1 AND "component" = apple

then link this ticket to

Issue 2 (release) which also has "fix version" = v0.1 AND "component" = apple

with "relates to" linked issue type