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

Fix-version no longer editable?

Dan Murphy2

We've been using fix-version to identify the target sprint in which a Jira issue should be fixed. Recently, this field has become un-editable by our users or simply no longer visible on Jira issue edit screens. What changed?

Google suggests that GreenHopper 5.10 (which I suppose we're using, as AOD customers) has switched to the "Sprint" field for this purpose, but I cannot find this field in any of our displays, either.

resolve-permissions.png

Accepted answers

Jobin Kuruvilla [Adaptavist]

Do you have "Resolve Issue" permission? You need this to change the fix Version.

If so, check if the field is on the screen and not hidden.

All comments

Jobin Kuruvilla [Adaptavist]

Do you have "Resolve Issue" permission? You need this to change the fix Version.

If so, check if the field is on the screen and not hidden.

Dan Murphy2

Yes, all our developers have "resolve issue" permissions. We've been using Jira and GreenHopper from the AOD servers for several months now.

Setting/changing the Fix-Version in the Jira issue view used to work, and now it doesn't. I can still edit the Fix-Version from the Agile Planning board (which has also become harder to find recently).

We didn't change anything w.r.t. configurations of our projects or AOD apps. This seems to be the effect of an "upgrade" breaking our existing workflow based on prior AOD recommendations... ;-(

Jobin Kuruvilla [Adaptavist]

If you can still edit the Fix-Version from the Agile Planning board, you are probably missing it on the screens?

Dan Murphy2

Correct, when I go to Jira and view an issue, Fix-Version is visible but uneditable and Sprint is not shown.

If I then select Edit, then select Configure Fields, select Display All, the Fix-Version field is not in the list of options, nor is Sprint.

Dan Murphy2

The thread between Kuruvilla and myself contains a usable resolution.

Andrew Nesterenko

Please see this article https://confluence.atlassian.com/pages/viewpage.action?pageId=711361820

It might be useful as well

Ankit Agarwal7

This was exactly what was needed.

C.J. Leth

I found a fix for my weird version of this bug, too: One of my projects randomly required me to go directly to the Versions screen in the Project Settings and add content there before it would allow me to manage Versions in the ticket screens. Note that once I added a Version once, I am now able to create new versions from the ticket view as expected. So I just had to do this once to "unbreak" it.

In Detail

I manage multiple projects all using the default JIRA field configurations, screens, and schemes.

ONE of my seven projects had this issue — While looking at the Create or Edit screen, the Fix Version field was not editable and had a value of "None".

I was able to fix it by visiting the administrator settings for the project and adding a random Fix Version to the Versions management area — Doing that enabled me to create new Fix Versions from the ticket screens as usual and add pre-existing Versions as expected.

André Cloutier

"Adding a random version" worked for me. Thanks!

The context: I moved a set of items to create a new project. That new project had no Versions set. I actually lost the value of fixVersion while transitioning issues from CLOSED to DONE. I just wanted to set them back...

Artem Tarashkevych

It works for me as well! Thanks

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

sprint

fix-version