Create and save multiple board views in business projects

[#1]

Hi Jira Community,

As part of the rollout of the new navigation, we’ve released the ability to add multiple board views (maximum of 5), to your business projects. Additionally, you’ll be able to tailor each board to your teams needs by applying view settings and saving them for everyone.

What to expect

We'll begin progressively rolling out these updates from March 2025, alongside the new navigation.

The key changes to look out for are:

• Project administrators will be able to create multiple board views in a business project.

• Project administrators will now have the ability to save the following board view settings for all users of the project:

  • filters applied

  • group by configuration

  • board card fields

  • selected workflow

  • column order

  • column collapsed/expanded state.

• Everyone with access to the project will have the ability to revert the board view to the last saved state.

• Project admins can rename all tabs (navigation items) in the project navigation in business and software projects. Project admins and board owners can rename the tabs in the board navigation.

Got feedback?

We’d love to hear your thoughts - drop your feedback and let us know what you think!

Thanks for being part of our community!

[__ Jimi Wikman]

I did not know that Jira Work Management was still available? Is this just for those that had it before the merge, or is this some kind of project type you can actually create?

[John Funk]

@__ Jimi Wikman  Jira Work Management is now just referred to as Jira - but there are two project types: Business - the formerly known as Jira Work Management; and Software - more or less formerly known as Jira Software. 

[John Funk]

@Yuan Jiang  - This is great news and has been needed for a long time. So if I am understanding correctly, an Admin (Jira or Project) can set a standard and save it based on filters selected, column order, etc. But the user will still be able to change things to modify those saved items for what they want to see. This will be maintained for them when they come back into the board each time. But if they want to go back to the standard Admin saved version, they will be able to do that. 

Is that the case? Is there anything I am misunderstanding? 

[chris sieverts]

This is very interesting @Yuan Jiang . Is there any plan to extend this to company-managed projects? Thank you

[Yuan Jiang]

@John Funk Yes your understanding is correct. To be more specific, non-admin individual user can use the "revert" button to go back to the project-level view set by their admin at any point of time. The "revert" button also serve as a signal to individual user, if they don't remember if they're looking at an individual only view or project level view 

@chris sieverts This feature is available for the board view in both Team-managed and company-managed business projects. Long term, we plan to bring these to all project types (software and business, team-managed and company-managed). We will likely do this view type by view type. Is there any particular view you're super keen for?

[chris sieverts]

Hi @Yuan Jiang I was not aware that it was available so thank you.

[__ Jimi Wikman]

@Yuan Jiang @John Funk That is interesting, and how would you go about to create a Jira project that is a business project? I see nothing in my instances that have that distinction and if they have a different code base, that is very important to understand when you create what type and what the impact of that would be?

[__ Jimi Wikman]

Ok, I see it now. The template will actually decide which configuration base your project will have... Do we have a list of these so we know what project will give a Business configuration (Work Management) and which will give a Software configuration?

[Jens Schumacher]

@John Funk: 

but there are two project types: Business - the formerly known as Jira Work Management; and Software - more or less formerly known as Jira Software. 

I believe the core difference is still company-managed vs team-managed. Albeit, it's rather confusing that there are now Software and Business projects as well. 

@Yuan Jiang 

What's the rationale behind creating even more project types? Understanding the difference between company and team managed is already a challenge. With Software and Business projects added to the mix, that confusion is multiplied. Shouldn't these just be different templates?