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/s field in Sub-tasks

Girish Jagdale

Fix Versions & Resolution fields are always displayed while priority and reporter are displayed and required as well. So we ensure that all required fields are added as they needs to be filled anyways to avoid error.

But why Fix Version is displayed and shows value as 'None'. Now as i haven't included this on my screen, users try to add value and can't do it. At least resolution is set to 'done' when closed.

Further issue type i'm referring to is sub-task which i believe shouldn't enforce to have fix version as main task itself take care of that.

I'm aware that i can set another field configuration and hide it but my question is why is that being displayed by default?

Accepted answers

James Hendrix

Girish, I think you should be more clear. Are talking ONLY about sub-task issues? Further, Fix Version is not a required field--in stories or in sub-tasks--unless it has been configured to be by your administrator.

If you are only referring to sub-tasks, then I would agree, it should either be removed or inherited (and therefore read-only) from its parent. You cannot release a sub-task, or at least that's not the way most people do it.

All comments

Andy Heinzer

FixVersion is a system field. If you remove it from the screen, users won't be able to change the value when editing the issue, but for system fields they still appear on the display. The same is true of other system fields like reporter.

I would recommend Penny's reply on this thread for more context: https://community.atlassian.com/t5/Jira-questions/Question-about-Fields/qaq-p/385794

It's not possible to delete the System fields, because many of them are associated with special behaviour in JIRA. However, if you don't need them you can hide them, which achieves the same purpose. The docs for this are here:

https://confluence.atlassian.com/display/JIRA050/Specifying+Field+Behaviour#SpecifyingFieldBehaviour-Hidingorshowingafield

FixVersion might not be very important to issues in Core or Service Desk projects, but it is critical to Jira Software issues and particularly to agile reporting that hinges on versioning data in order to organize that information.

Girish Jagdale

But point is, for sub-task, i don't need to have a fix version. As mentioned it will be for parent task which is defect in my case.

I went through other links earlier but I'm more concerned about sub-tasks type that shouldn't have this field by default.

James Hendrix

Girish Jagdale

Hi James,

I looked in some other post to find the answer and try & test and Nic Brough's explanation helped it rightly.

What i want is simply not have fix version/s disappear from the sub-tasks.

Now if it would have been custom fields, it was easy to go screen and remove it. But for built-in (standard fields), the only way to make them hidden from field configuration for issue type.

James Hendrix

Glad you found what you were looking for. In case anyone else lands here, the following threads provide great insight:

Daniel Holmes

Yea, I agree with this point. I also have the case where subtasks just track work assignments to both Affects Versions and Fix Versions have no meaning as it is the parent bug/story issue that is tracked to a release version. Would be nice to not confuse developers with these fields on subtask displays