Are tabs deprecated in Jira Cloud New Issue View, and how should fields be organized now?

[damir_khamidullin]

Hello,

I would like to confirm whether the following assumption is correct: that screens with multiple tabs in Jira Cloud have been gradually phased out, and that the Classic Issue View - which supported tab-based layouts - has been replaced by the New Issue View, which no longer displays tabs or provides an equivalent way to logically organize fields.

In our project, we have a large number of custom fields that need to be logically organized. Using tabs appears to be the most reliable solution for grouping related fields. It is important for our workflow that these tabs remain visible on the Create, View, and Edit Issue screens to maintain a clear structure.

Thank you in advance for any clarification.

[Arkadiusz Wroblewski]

Hello @damir_khamidullin 

Yep, your assumption is mostly right  not because Atlassian “deprecated” tabs, but because the New Issue View doesn’t handle screen tabs the same way the Classic view did.

In Classic, tabs were a reliable way to group fields and keep that structure visible on Create/View/Edit.

In the New Issue View, even if your screen has tabs, Jira may not show them consistently on the View screen, and it can also “reshuffle” fields into its own sections. So tabs aren’t necessarily gone, they’re just not a dependable UI-structure anymore.

How I’d approach it in Cloud:

Use the Issue/Work item layout to control order + visibility, and hide fields when they’re empty/not needed.

Keep Create/Edit focused on what users must fill in, and push the “nice to have” fields further down or hidden.

And honestly: this kind of configuration is always a bit of an art. There’s no perfect template, it needs to be fitted to your workflow, your users, and your company’s way of working. Best results usually come from starting simple and iterating based on real user feedback. 😉