JWM List/Board Settings Not Saving - Bug or WAD?

[Alison Clough]

We have recently purchased a small number of licenses for JWM. We are noticing that many of the settings on the List view revert to defaults as soon as you leave the List tab. This includes grouping settings, expand/collapse settings, and even changes to columns setup (order/additions/removals). All filters are stripped when you access a project. Once you set them, they "stick" as long as you remain in the project.

On the Board view, the grouping is retained. However, filters behave the same way as the List view (are cleared when you exit the project).

This is a EXTREMELY frustrating behavior, as you have to reset things every time you access a project. For us, this is likely going to be a deterrent from our using the application at all.

Is this a Bug or is this the way the product has been designed? I've taken a look at Atlassian's support site and see both bugs and feature requests that allude to similar complaints. So, it is hard to tell if this behavior is a bug that may have a fix coming soon or is considered working as designed. I have to believe that this is a Bug and that Atlassian wouldn't design a product to behave this way.

[Ben Payne]

Hi Allison, my name is Ben - I'm a product manager working in JWM.

Sorry you're having a frustrating time with persistence across filters, grouping, expand/collapse and more. This is on our radar and something we're looking into fixing soon. To answer your questions individually

• List view columns, both the columns themselves and their ordering, should persist  after you navigate away from the list tab or project itself. This sounds like a bug.
• Filters should persist on a view when navigating to other views in your project. This is a bug we know about and plan on fixing
• As you pointed out grouping in list and board are inconsistent. Both should persist on the view when navigating around a project. We're planning on fixing this.
• Persisting expanded hierarchy is not something the team has considered. I appreciate it's annoying when moving between views - it's something we'll look into.

At this point there is no persistence when moving across projects, this is however in our long term roadmap.

Thank you for feedback, please don't hesitate to ask more questions in this thread!

[John Funk]

Hi @Ben Payne  - Thanks for the information! Are there JAC tickets for these that we can vote for and follow? 

[Hannes Obweger - JXL for Jira]

Hi @Alison Clough

not sure about bug vs. WAD, but these things have been brought up a couple of times here, so I'd assume them to be on the team's radar. If you haven't already, I'd recommend to upvote and watch the respective bugs/feature requests; from my experience, this does make a difference.

[Hannes Obweger - JXL for Jira]

... and just to put it out there: I acknowledge that these issues, by themselves, may not justify additional tooling, but if you're open to it, you may like the app that my team and I are working on: JXL for Jira.

JXL is a full-fledged spreadsheet/table view for your issues that allows viewing, inline-editing, sorting, and filtering by all your issue fields, much like you’d do in e.g. Excel or Google Sheets. In a sense, it has some things in common with JWM's list view, however it comes with a range of advanced features, and also works in (and across!) projects of any type, not just JWM projects.

Plus, all your view preferences - be it grouping, filters, or your issues' expanded/collapsed state - are always persisted, so you'll always find your JXL sheet just like you left it.

This is how it looks in action:

Any questions just let me know,

Best,

Hannes

[John Funk]

@Matthew Canham