Manage the transition to the new issue view

From March 31, 2021, we’ll move all users on the old issue view in Jira Cloud products (Jira Software, Jira Service Management, Jira Core) to the new issue view. — which means that soon your users be able to switch back to the old view anymore. For a limited time, they’ll still be able to temporarily click through to the old issue view.

Read on to learn how — as an admin — you can best set up your team for success in the new issue view, and how to use the admin controls to manage your transition. Learn more about our transition plan to the new issue view

Why are we moving everyone to the new issue view?

The new issue view was designed with a flexible layout so admins can configure where fields live to fit their team’s needs. This means it can be customized to work with every team, unlike the old view which has a one-size-fits-all layout that may not work for everyone. If the new issue view doesn’t work for you, leave us feedback by going to an issue and clicking Give feedback().

By transitioning everyone to the new issue view, we can focus on a single issue experience and ship more features faster. The new issue view is built on an infrastructure that enables us to easily build and support more features. For example, smart searching, integrations with other Atlassian products, and SLA support are only supported in the new issue view — and there’ll be many more to come.

What’s changed for admins?

Flexible issue layout

The new flexible layout means you can change where fields live on an issue depending on what suits your team. Below is a breakdown of the different sections in the new issue view.

Annotated screenshot of the new issue view labelling the different field areas
  1. Description fields: The default Description field, other multi-line custom text fields, and other important fields go here. Since this is the first place someone looks when they see the issue view, we recommend putting your most important fields here. This section usually appears on the left side of the issue (or at the top in a single-column layout).

  2. Context fields: Contextual information to help you sort, filter, and report on issues. Each user can pin these fields to stick the ones most important to them at the top of their view. This section normally appears down the right side of the issue (or at the bottom in a single-column layout).

  3. Show more: The context fields section also has a divider you can use to sort always-important fields from sometimes-important fields.

  4. Configure fields: Move, hide, and change fields in the new issue view.

Issue layout page

From the new issue layout page, you can choose not only where in the layout your fields are displayed, but their order and whether they’re shown at all. Since this page didn’t exist for the old view (you can’t customize its layout), you may want to configure your issue layouts when you move to the new issue view. Learn more about configuring field layout in the new issue view

Screenshot of issue layout configuration page for new issue view in Jira Cloud

To get to the issue layout page for an issue type, either:

  • Click Configure() at the bottom right of an issue or

  • From your project, go to Project settings () > Issue Layout, and then choose an issue type.

View and edit from one screen

The new issue view has just one screen where you view, edit, transition, and comment. Just click any field you see to edit it inline (if editable). The view and edit screens decide whether you can view a field, edit it, or both. This means if a field is in the view screen but not the edit one for an issue type, it’s a read-only field and you can’t click to edit it. Learn more about managing screen schemes

Jira Cloud - Inline edit fields in issue view

When do you want to move your users to the new issue view?

March 31, 2021

No actions from you — we’ll take care of it. We’ll remind your users of the change so they get enough time to prepare, and then at some point during April, we’ll move them over if they haven’t done so already.

Example pop-up reminder in Jira

Example modal of the pop-up reminder in Jira Cloud a user will receive if they're on the old issue view.

Before March 31, 2021

If an earlier date suits you, you can move all of your users to the new issue view before March 31, 2021 by using the new toggles we’ve added.

Maybe the new issue view is already ready for your team, or perhaps you want to wait for a specific feature before your move. When you’re ready, follow the instructions below.

Move your users to the new issue view all at once

You can move your users to the new issue view before March 31, 2021. After that date, this option will no longer be available.

You must be a Jira admin to move your users before March 31, 2021.

Screenshot of new issue view transition settings page in Jira Cloud

To move your users all at once before our date:

  1. Go to () > Issues > New issue view transition.

  2. Toggle on Delay new issue view reminders. Since you plan to move your users to the new issue view before our date, this prevents your users from receiving the incorrect date from our pop-up reminders (example above).

  3. Using your preferred method of communication, let your users know when you’re going to move them to the new issue view, so they get a heads up on what’s coming.

  4. When you’re ready, toggle on Move all users to the new issue view.

Your users on the old view will receive onboarding back to the new issue view with an optional tour of key and latest features we’ve added since they’ve last seen it. They’ll still be able to click through to the old issue view to complete a task until some time after March 31, 2021 where we remove the old issue view altogether.

You can let your users move back to the old issue view until March 31, 2021, by toggling off Move all users to the new issue view. This won’t move them back automatically, but they’ll be able to switch back from their personal settings.

When am I ready to move my team to the new issue view?

If you’re not sure whether you’re ready to move everyone yet, give the new issue view and try and see if it works for your team. It’s received a lot of improvements since we first released it and will only get better as make sure it’s the best view for everyone.

If you’re waiting for a specific feature before moving, you can track them by watching linked issues on JRACLOUD-70555. All issues with the “in progress” status will be resolved before we move everyone to the new issue view.

Last modified on Mar 5, 2021
Cached at 9:01 PM on Mar 6, 2021 |

Additional Help

Ask the Community