Fix versions missing from Story work type after editing required setting.

Question

Site: velos-team.atlassian.net

Project: VELOS (Velos Geral), team-managed software project

The Fix versions field works correctly on the "Problema" (Bug) work type, where it lists all nine existing project versions. However, it disappeared from the "História" (Story) work type right after I edited that field's required setting.

The REST API confirms the field is genuinely unassociated, not just hidden in the UI:

- Create metadata for the História work type returns 21 fields with no fixVersions entry, while the same call for Problema does include it.

- An attempt to set fixVersions on a História issue (VELOS-43) was rejected with: "Field fixVersions was not found in the project's issue type metadata."

The field still appears under Fields in the work type configuration and in global fields, and removing and re-adding it there had no effect.

The documented workaround is to toggle the Releases feature off and on in space settings. However, Releases does not appear at all under the Planning section of my space features (only Sprints and Estimation are listed), so I cannot apply it.

This appears to match known bug JRACLOUD-93444.

Has anyone found a way to restore the Fix versions field on the Story work type, or to bring back the Releases toggle in a team-managed space?

Josh · Answer

On team-managed software projects, “required” toggles can desync the field from a work type’s layout.

Try this order:
 1. Project settings → Work types → Story → make sure Fix versions is still on the layout (Create and Issue view).
 2. If you marked it required, switch it optional, save, then required again — that often rebinds the field after a layout edit.
 3. Confirm Fix versions still exists under Project settings → Versions / Releases (empty or deleted releases can make the field look “gone” on create).
 4. Hard refresh / try an incognito window — team-managed layout changes sometimes stick on a cached create form.

Bug work type still showing it usually means the field is fine at project level and Story’s layout lost the association. If it still fails after re-adding to the Story layout, note whether you are on the new “work type” UI or classic — that helps support reproduce.

Trudy P Claspill · Answer

Hello @Everton Precaro

For clarity when @James Gamble says to toggle Releases through Space Navigation he is talking about clicking the + at the right end of the view tabs and adding Releases from there.

To toggle it off you would find the Releases tab, click the eliipsis button, and select Remove.

On a side note be advised that this is a user community populated mostly be other Atlassian customers like you. We don't have access to your environment to look at anything directly.

Also this forum is publicly accessible on the internet. As such you may not want to post your site's URL in any posts and you may want to edit your current post to remove it.

James Gamble · Answer

Hola Everton,

I think there’s a path here that’s worth trying before treating this as a stuck field configuration.

Your REST results are useful because they confirm that Fix versions aren’t merely hidden from the Story layout. Jira really isn’t exposing fixVersions in the Story work type metadata, while it still does for Bug.

The workaround you found is legitimate. Atlassian documents that team-managed spaces can enable Releases through the space navigation, and enabling Releases adds the Fix versions field to the space’s work types.

What’s interesting in your case is that Releases itself is missing from Space settings > Features. Atlassian’s current documentation provides another way to enable the Releases feature in a team-managed software space: Space navigation > Add to navigation (+) > Releases > Add to navigation.

That isn’t just adding a shortcut. Atlassian describes it as another way to enable the Releases feature, which is why I think it’s worth trying in your case. After doing that, I’d go back to: Space settings > Work types > História and check whether the Fix versions have been restored. I’d also repeat your create-metadata call afterward to see whether fixVersions has returned for Story. There’s also a very similar Community case where Fix versions disappeared from an existing work type, and toggling Releases restored it.

One small note on JRACLOUD-93444: that Bug is marked Fixed and was originally about Fix versions not being available on custom work types in team-managed spaces. Your symptom is a little different because História is an existing built-in work type, and the field disappeared after its configuration was changed.

If Releases also doesn’t appear under Add to navigation, then I think you’ve got a stronger case for Atlassian Support, because both documented ways to enable the feature would be unavailable, even though the space already has versions, and Fix versions is still working on another work type.

Thanks,

James