+1

Our wish is three options to choose from for the column settings: a) individual user setting b) System or project admin setting as default c) Jira basic setting as fallback-option.

The chosen setting should should be saved for the list / filter / issuetype individually for each user. It should than be the same on all Devices and Browsers once you lock in your account. 

+1

+1

+1

+1

Would like to create easily usable predefined views where inline editing is possible. Admins could have the option to either "lock" the configuration or open it so everyone could use their own. 

This feature is very much needed for our company!

This feature is highly needed and extremely important for us. Without it, working in the current setup is very inconvenient and time-consuming. Implementing this functionality would greatly improve efficiency and ease of use for all involved.

Made the 400th vote. How many more are necessary? Please implement this feature as I want to be able configure, present and explain the same List view for all of our users.

Yes, this is a much needed feature for our organization. Please continue to consider this & provide updates!

We would appreciate this feature as well! Since we work on many different projects at the same time, configuring the list for each is a hassle. Also, the configuration resets when deleting cached browser data, which is a unfortunate.

Yes please

We would greatly appreciate this feature. While personal customization is nice, it has been requested by our project teams to have a standard list view that would display for all team members consistently and we are unable to do this for them as things currently are. Thank you for considering!

"Set View as Project Default" and ability for admins to modify the default view at the org. level is a must! 

3 years since this issue was raised. It's got to be close, right?? /s 

Because we are in a project driven environment, we have many projects in Jira. Changing the default columns for a list view by project/users is annoying. It would immensily help to be able to specify the default columns on the Jira admin level, valid for all projects. No fine-grained configurability needed.

Our team also needs this feature, please let us know as soon as it is available. That's particularly important to work properly with our team and share as admin same view without asking to each person we include in the project to readapt the view, it's also time consuming.

Our team also needs this feature! It's so annoying to edit this List View every time you change your PC or browser. It can be reset suddenly, and you need to reconfigure it again and again for every project in which you are participating especially if you have custom fields and need to monitor them. Really waiting for implementation of this option.

There are no words that can describe how important this issue is. I cannot convince team to use the list view because they cannot setup columns as: 1st issue symbol, 2nd Summary. That is crucial to have THE LIST view. Right now Jira won't let relocate first two columns with issue symbol and issue key. That is really annyoing. Please let us know when this will be released.

We cannot convince teams to move from tracking project progress in Excel to Jira until this feature is enabled.

Our team needs this feature as well

Being able to set a default view as the admin would be fantastic, but even just having the user's column changes stay as they are set is critical. I have business stakeholders literally asking if we can use another software solution (rather than Jira) because they have to keep setting up the column views to our standard view after it mysteriously resets to the default columns randomly and frequently. And thats to not even mention what my external clients have to do but just haven't reported yet.

It's hard to overstate how important this is for non-IT, non-admin users on boards that use heavily customized fields and views.

Does anybody know of an API or marketplace solution for this that could work in the mean time?

Please let us know when this is released?  My team needs a predefined/default list view set for all of them.  it keeps going back to the old list view and we have to change it every time!  so annoying.  

Our team needs this feature as well. Is there any plan currently to release this feature?

Our team need this feature as well!

our team need the same feature +1

Badly needed feature

We require this as well!

Commenting to add that this is causing us to reconsider using Jira. Smartsheet has so much more flexibility and the fact that the columns order can not be saved and must be changed each time we login is a dealbreaker. 

Hi 83507815dafe :

Yes, of course we absolutely need to continue to have default project view.  My previous comment is not about removing/replacing it.  It is about re/naming the two "List VIew"s such that we can communicate about it without confusing one with another.  May be:

• Rename the Project issues "List view" as "Issues List View" and
• Rename the JWM List View as "Work List View" (or something better)

Note that JWM list view allows inline editing but it does not support fields like "Linked Issues" which is supported in default "Issues List View".  On the flip side, you can save/share filter for your default "List View" with your fields column preserved which at present you cannot do with JWM share feature.

I am optimistic about Atlassian JC roadmap to continually improve the overall UX

This is a hard requirement for our company.  We need to have a default list view on a per-project basis.  

First thanks for making JWM part of JC as of Teams'24 event.

I am voting for below three capabilities with JWM "List View"

1. Provide support for below additional fields to be added as columns
   1. Linked Issues
      1. If you select "issues" in the left pane then you can add "Linked Issues" as a column but this is not possible with JWM "List View"
   2. Multi-line fields like Description (We have this in issues based "List View")
   3. Support for all other data types that are supported in issues based "List View"
2. Ability to save/share my "List View" with users/groups as view/edit (similar to how filters/dashboards are shared).
   1. Note: "Share" feature is there but it is NOT sharing the field config.
3. Rename the "List View" on issues screen to something else so it does not confuse with JWM "List View"

Many thanks,

Piyush

In my opinion, it is reasonable to have a default view for the ListView/s.

This has been a real problem for us. Can this feature be prioritized accordingly so that one can save the layout of the List view after selecting the needed columns?

https://getsupport.atlassian.com/browse/JST-994001

Huge fan of JWM but this can make or break our utilization of this tool.  As project admins it's an annoyance and we can reset the columns but its counter productive and for our customers, users, and our project teams they live by the UI so this is not project friendly.  Where is this in the JWM roadmap to be fixed? What is the timing for a solution?

An admin or Project Lead of a project should have the ability to set a default list view for the full team.  But the team member itself should also have the option to change the list view according its own needs, but can always revert back to the default.

Especially with onboarding new Jira users (who never ever used Jira before)  they really struggle with getting the same view as their Project Lead. So literally they have to sit next to each other and check back and forth to see how the other has set the list view and copy it manually.

If then managers and directors also need to look into the project, the first thing they need to do to understand the project, is to amend the settings of the list view first in order to see the data they need to understand.  This is really frustrating and time consuming. 

Hi everyone,
My name is Eric - I'm a Product Manager working in the Jira Work Management team at Atlassian. Thanks everyone for voting and commenting your feedback below. I would love to learn more deeply about your use cases and understand the problems this feature request would solve for you.

If you’re interested in chatting to me about this, please grab a time on my calendar via this link: 30 Minute Meeting - Eric Zheng

Looking forward to speaking!
Eric

Any hidden or added fields should also be reflected when the list is embedded into other places (e.g. Confluence). 

Sharepoint had predefined / custom list views somewhere in 2000 ... Jira in 2024 ... heh

This is extremely important, causes so much unnecessary work for employees in my workplace and instant dissatisfaction when bringing them across from Monday.com where this comes naturally to this.

Also, you offer consistent views in your other products, so why not this one.

This needs to be bumped up in priority.

Yeah. Kind of crazy we cant control what fields our users see in a project. Each project has different fields for us.

There is a query parameter that can be used to control the grouping. It's a partial solution but when you group the query parameter ?groupBy= is added and you can bookmark that to keep the grouping each time. 

Jira doesnt have this feature??? For bigger teams (more than one person heh ...) this is a must!

I have set up a project and custom fields in the list and all custom fields "dissapered"/didn't show up to other team members - they have default list view which is useless!

100% agree with this enhancement, The ability to create specific views (including with custom fields) for a JWM project would is a much needed feature. Not having this creates extra effort for each person in the team, we have to create videos and supports about how to add the view back to how it was before. I should be able to set this as a project admin and that is the view for all on the project.

Same here. We want to create one or more specific views (including with custom fields) that should be the same for every user/viewer.

Quand peut-on espérer une résolution de ce problème ? Malheureusement cela génère beaucoup de frustration dans les équipes. Nous avons quitté Asana pour Jira, malheureusement certaines fonctionnalités sont manquentes sur Jira. Et notamment celle de filtre/vue par défaut.

Very much hoping this is added soon. Is there an ETA? It would make a huge difference to be able to standardize the list view for everyone so the most pertinent information for that project is visible rather than being overwhelmed by all the info (some of which might not be relevant).

We have started using JWM as a Monday.com replacement. We are finding that this bug is causing additional work and frustration to my team. Any ETA on a resolution? Please prioritise this bug and resolve it as soon as possible. Many thanks

Hello there, we have also started utilising JWM as a replacement for Monday and this bug is causing issues and taking up additional work time for our team having to set up their list view each time this occurs. Is there an ETA for this being resolved? Thank you 

Hi there, we've recently started using JWM as a Monday.com replacement. This issue is causing a lot of issues for us. Is there an ETA on when this might be resolved? Thanks  @Patric 

I can't believe this hasn't been implemented yet. JWM is so dumb without this.

I have an Enterprise Package of Jira, but I am unable to use the Jira Work Management due to this silly bug, Please prioritise this bug and resolve it as soon as possible, I am seeing around that many users are not moving to JWM due to this silly bug.

This functionality is integral to getting my team to utilize JWM. I cannot champion using this product when every individual user has to customize their view, sometimes daily if their cookies are cleared. This coupled with not being able to use user created custom fields in the advanced roadmaps, there is no workaround for this lack of capability.

This is the #1 feature that keeps our business users blocked on moving from asana to JWM. If those teams moved to JWM then we could also use Confluence and Atlas more effectively to manage work across our organization. The issue is that they want to use the list view with a group by automatically applied and specific columns visible by default - this is so they can mirror the setup they are used to in Asana. One simple fix would be huge for our organization and 3x the # of people who we have using Atlassian products.