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

"Affected Versions" visibility in releases menu

LAL_i6rck1

In the Releases menu only issues that have "fix version" matching the release version are shown.

How can I also show issues that have affected version matching the release version I'm looking at?

We use affected version to mark version where the issue was found and fix version for the version where the issue was fixed. Our release notes primarily list new issues related to the release. Is this possible with releases menu?

We could use the releases menu to create release notes to confluence, but currently we cannot use this due to issues affecting the version not being visible.

Accepted answers

Jens Schumacher_3blqvj

Releases in Jira are designed to work with issues that have been resolved or were scheduled to be resolved in the specific version.

As such, it’s not possible to include issues that that are affected in a version. Still not quite sure I understand the usecase to be honest.

With that being said, if you require a little more flexibility, you could take a look at apps like Released [1], which generate release notes for you and provide more flexibility around what issues to include in a post.

[1] https://marketplace.atlassian.com/apps/1230872/released-ai-release-notes-and-roadmap-automation-for-jira

Marc -Devoteam-

Hi @LAL

Affects versions and fixed versions are values that are picked up from the jira releases/versions in the project.

So they are essentially the same, but used in different contexts.

As you stated, yes you are using the fields in a correct way.

And yes I do see your point in this to have affect versions information shown in the Releases menu. But this is not an option.

A similar question has been asked before, but declined, see JSWCLOUD-15522

All comments

Jens Schumacher_3blqvj

Releases in Jira are designed to work with issues that have been resolved or were scheduled to be resolved in the specific version.

As such, it’s not possible to include issues that that are affected in a version. Still not quite sure I understand the usecase to be honest.

Marc -Devoteam-

Hi @LAL

Affects versions and fixed versions are values that are picked up from the jira releases/versions in the project.

So they are essentially the same, but used in different contexts.

As you stated, yes you are using the fields in a correct way.

And yes I do see your point in this to have affect versions information shown in the Releases menu. But this is not an option.

A similar question has been asked before, but declined, see JSWCLOUD-15522

LAL_i6rck1

I'm disappointed but it wasn't totally unexpected that this kind of usage is not supported. A lot of Atlassian features feel lacking.

For the usecase it's pretty simple, we release software for business clients depending on their schedule. When a request for new release is made, the release notes associated with that release need to state what bugs are to be expected. This way our client can avoid costly known issues related with non-final software.

Thanks for the app link, but thats bit too much for our needs

Anand Inamdar_Amoeboids

@LAL I have seen your responses above and can empathize with your situation.

May I recommend looking at our free app that will easily solve this problem - https://marketplace.atlassian.com/apps/1223567/free-ai-powered-automated-release-notes-reports-for-jira

The free version does not have any limitations in terms of what information you can include in the release notes. And works pretty well for many teams with limited automation needs. The way it will work is - you will include two JQLs in the release notes template - one that retrieves issues fixed in that version and another one that retrieves issues that are 'affecting this version'.

Give it a try and if you need any help, do reach out.

Best,

Anand

PS - I lead the team that develops and maintains this app. The free app is our way to give back to the Community.

Jens Schumacher - Released_so

Understood. So these are bugs found during internal testing that are proactively communicated with the customer. That makes sense.

Eva Deichner

Hi guys, i have the same issue as other users missing the bugs in the release notes that have the release as the affected version.

i then tried to create an own Release Note with the Xporter.

unfortunately i was not able to get the list of these bugs in the document. Could you help me with the code? KI couldn‘t help.

Thanks a lot

Welcome!

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

Quick Links

Unanswered
Groups
Help

Find more posts tagged with

jira

cloud

jira-cloud

release

release-note