Group by labels in advanced roadmap not visible to other users

[Esther Strom]

One of my users has created a plan that she's grouped by labels in the view settings. None of the other users (including me as a site admin) can see the changes she's made to the view; we're still seeing the default sorting/grouping hierarchy. (The labels already exist on the tickets in the plan; they were not added via the plan but not applied to the underlying tickets.)

I've done a screenshare with her and she's definitely saved the changes to the view. Any idea why no one else can see the view changes?

This is what the user in question sees (the view is showing unsaved changes because she collapsed all of the ticket hierarchy; it had been saved after the grouping was created.)

This is what I and the rest of our users see:

(Also, is there any limit to the number of label groups you can create?)

[Omar Rashid]

In case someone else is looking for the answer to this:

If you simply share your roadmap URL , the groupings via label will not be preserved. You have to click on the 'Share' button and use that link and then the groupings via label are preserved :-) 

[Mark Segall]

Hi @Esther Strom - Note that the view says "Basic - Edited".  Make sure that the view has actually been saved otherwise the view is in a draft state that only the person changing can see.

As to the second question, I'm not 100% on this, but I believe it's 50

[Esther Strom]

Hi, Mark - that Edited mark was, as mentioned, because the user making the changes had collapsed all the tickets. The actual grouping change had been saved. And that brings me to the solution we found. 

Apparently even just expanding or collapsing a heading while scrolling through a large view is enough to trigger the Edited flag, and that means that even if a user made real config changes and saved those changes, someone else who is navigating that same view who's expanded a different set of tickets will not see the changes unless they click the Revert option under the view name button. I find this to be really unintuitive; in no other system would simply expanding or collapsing headings be considered an actual configuration change to a view that needs setting. If I view a Confluence page that has a set of expanders and expand one section, it doesn't prompt me to save the page; why would it do so in a plan? Only actual config changes make sense to save.

[Mark Segall]

Yes, I share your confusion on this as well and would agree that putting the view in "Edit" mode only makes sense for actual changes to the filter/view settings.  I'm looking for a Jira suggestion on this, but haven't found it.  Perhaps someone else in the community has seen a suggestion that can be shared here so we can all vote for it.

[Esther Strom]

Yeah, I've checked jira.atlassian.com as well, but my JQL-fu is failing me. 

[Noah Miles]

Thank you Esther!  The mystery is solved!