"Fix Versions" can't be added to "Task" type

[Clark Holdham]

I can't seem to add the field "Fix Versions" to the issue type "Task". It's already a member of "Story", "Bug" and "sub-task". I have a team managed project.

[Trudy Claspill]

Hello @Clark Holdham 

Welcome to the Atlassian community.

What exactly do you mean by "can't"?

Are you not able to find the field when you search for it? If so, have you confirmed that it is not already added to that issue type?

If you do find the field when searching, are you having trouble dragging and dropping it into the layout for that issue type?

If you are successful in dropping the field in the layout, then are you encountering some error trying to save the change?

Or is the issue that the field is already present, but is hidden when empty and appearing in the More Fields section under the Details panel for the issues?

[Clark Holdham]

It's not listed as a field in the issue or in the right hand column.

It is however listed on other issue types

[Trudy Claspill]

TL;DR

Try disabling the Releases feature for the project, then re-enabling it. That should add the Fix Version field back to the work item type layout.

I removed the Fix Versions field from an item type and saved the change.

I immediately tried to search for the field and re-add it, but searching did not find the field.

I haven't left the Project Settings area so far, so I went back to the project view and then back into Project Settings. Still couldn't find the field when using the field search panel.

I did an internet search and found this fixed issue.

https://jira.atlassian.com/browse/JRACLOUD-93444

That prompted me to check if the Releases feature was enabled in the project. It was.

So I disabled it, then re-enabled it.

Then I went back to the item type layout where I could not previously find the Fix Version field in the field search. I found that the field had been added into the item type layout simply by me having disabled then re-enabled the Releases feature for the project.

That solution is mentioned in a Work Around in another issue:

https://jira.atlassian.com/browse/JRACLOUD-93444