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.
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... ;-(
OK, for those following along at home...
Select Administration, then go to the Issues tab and expand the Screens option.
Find your "default" screen, select Configure (not Edit) and use Add Field to put Fix-Version/s back in the default screen (even tho its displayed already). Hit Add and then navigate to an issue with a previously uneditable Fix-Version/s field -- voila!!
Thanks for the tips everyone. Unfortunately, even after following the detailed steps above, both Fix Versions and Affects Versions are still not editable for us. We see them on every issue, versions have been added in the admin, the default screens have been configured (by removing and then re-adding the fields similar to what is described above), but there does not seem to be any way to edit their values when looking at an issue.
I'm new at Jira, so, please be kind and detailed in your replies.
Ha! Just fixed it myself!!
Now, I realize that I am probably modifying more than I need but in our case it's ok since we intend to use these fields everywhere. It would be very helpful if someone could explain to me why this approach worked while the steps indicated by @Dan Murphy did not (for us).
Thanks and good luck!
None of the above resolutions worked for me, I can see that the fix version is included in the default screen config and it is visible in my workflow associated screen by transition. I can see the field but it is not editable in both transition view and in edit issue view.
Ok I solved it for me, I had to add the 'Administrators' user group into the 'Resolve Issues' permission as a associated project role. Weird, I just assumed that project admins would have permission to do all tasks. So basically I ended up with 2 project roles associated with the 'Resolve issue' permission, 1 for developers and 1 for administrators.
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.
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.
The wait is over... Portfolio for Jira Server and Data Center 3.0 is now officially here! Platform releases offer Atlassian an opportunity to shift our strategy, make bold predictions about t...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs