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

Linking development tickets to releases

michelle_anderson_6xg669

What's the quickest way to link development tickets to a release in Jira Cloud? For example, there maybe 100's of development tickets that need to be linked to a release and I'm seeing if anyone knows a quicker way than downloading to an excel spreadsheet and then copying them in please?

Accepted answers

All comments

Trudy P Claspill

Hello @michelle_anderson

How do you select the issues that need to be linked to the release?

If you can develop an issue filter that will select the issues, then you should be able to use the Bulk Change feature to set the related Versions field in the issues to the specified release version.

michelle_anderson_6xg669

Hi Trudy

The fix versions are already set. I do run a filter so I can see all the development tickets associated to a release, that's not a problem. I was asking if anyone knows a quick way of then linking all the development tickets in a quick way to a release, rather than having to link each development ticket individually to the release ticket.

Michelle

Trudy P Claspill

Thank you for that additional information. I now understand you are trying to create links between one issue (release) and many other issues (development).

From the Release issue you can link multiple issues to it, but you have to type in and select each Development issue key.

The Bulk Change feature does not support selecting multiple issues and then linking one issue to all of them.

Natively, the only method to do this would be to use an Automation Rule. In the rule you could execute a search for the Development issues and then loop through them to link each one to the Release issue.

If this is a task you need to do repeatedly for different Fix Versions (sets of Development issues) and different Release issue, you could create a Manually Triggered automation that prompts for input. The Input could be the Fix Version name and the Release issue key. Those inputs could be used in the rule to execute the search for the Development issues and then specify the Release issue to which they should be linked.

Screenshot 2024-12-20 at 9.31.01 AM.png

Screenshot 2024-12-20 at 9.31.35 AM.png

michelle_anderson_6xg669

Thank you, Trudy I will give this a try.

Kindest regards

Michelle

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

jira-work-management