I'm setting up a new Team Managed project in JIRA Cloud, something I've done many times before.
I'm having trouble adding the "Fix Versions" field to some Issue Types (sorry, "Work Types", going to take me a while to get used to this peculiar change!).
Like I say, I've done this many times before, and I've never had this problem before. I have created this project using a steps which I recorded in a confluence page a few years ago and have used several times before without problems.
It's showing up by default in "Task" "Subtask" and "Epic" but it's not letting me add it to "Bug" and "Story".
Releases feature is enabled (and I created a Release just to check that it wasn't refusing because of the lack of options).
When I type in the "Search fields in this project" text field, it tells me "No fields in XXX match that search".
But Fix Versions is in the Epic/Task/Subtask types, and is listed on the global fields page.
I had to add Bug and Story types after creating the project, I'm guessing it might be related to that in some way.
Any ideas? It's particularly important that we have it in the Bug type!
Hi @Rupert Ward -- Welcome to the Atlassian Community!
Do you have any custom Work Item Types (formerly called Issue Types) in the project?
If so, I wonder if it is related to this open defect for team-managed project types / field configurations: https://jira.atlassian.com/browse/JRACLOUD-93444
The workaround described is:
Kind regards,
Bill
Yes, we do have some custom dropdowns.
And yes, that has fixed it.
Than you ever so much!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Rupert Ward and Welcome to Atlassian Community!
Just to be sure, is the Release option enabled in Project Features?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, Releases feature is enabled.
I've also created a Release just to check that it wasn't refusing because of a lack of options to put in the field.
Good thought though, I should have mentioned that in the question (and have added it there now for completeness).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.