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

How to block the usage of a "Fix Version" if it has already been Released?

Pedro G. Ferreira

Is there any to configure the "Fix Version" field to not display the already Released versions?

Accepted answers

Fabio Racobaldo _Catworkx_

Hi @Pedro G. Ferreira ,

released versions should be selectable on the Affect Version and not on the Fix Version. There is a open ticket for that https://jira.atlassian.com/browse/JRACLOUD-39618

Please vote and watch it!

Fabio

Bill Sheboy

Hi @Pedro G. Ferreira

Do you mean: do not show the "released" versions in the drop-down list for version selection?

If so, you can "archive" them after they are "released" (on the versions page) and they will not display in the drop-down lists.

Kind regards,
Bill

All comments

Fabio Racobaldo _Catworkx_

Hi @Pedro G. Ferreira ,

released versions should be selectable on the Affect Version and not on the Fix Version. There is a open ticket for that https://jira.atlassian.com/browse/JRACLOUD-39618

Please vote and watch it!

Fabio

Bill Sheboy

Hi @Pedro G. Ferreira

Do you mean: do not show the "released" versions in the drop-down list for version selection?

If so, you can "archive" them after they are "released" (on the versions page) and they will not display in the drop-down lists.

Kind regards,
Bill

Pedro G. Ferreira

Hi @Bill Sheboy .

That's exactly the behaviour we are looking for. But by archiving the version, doesn't it also makes it unavailable at the "Affects Version" drop-down list?

We need it available at the "Affects Version" but unavailable at the "Fix Version".

Thanks,

Pedro

Pedro G. Ferreira

Hi @Fabio Racobaldo _Catworkx_

Thanks for linking to the existing issues. Thats exactly the required behavior.

Thanks,

Pedro

Bill Sheboy

Thanks; I missed that part earlier.

And it seems a better feature would be two "levels" rather than the one for "archive", as the current feature implies "this version no longer exists in production, and so cannot be assigned" versus "released, and exists in production so defects could be found".

Pedro G. Ferreira

That approach would also answer the requirement!

Fabio Racobaldo _Catworkx_

you're welcome @Pedro G. Ferreira

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud