Calendar Layer Selection Should Remain In Place When Advancing

Bug #924520 reported by Nat Katin-Borland
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
KARL4
New
Undecided
Nat Katin-Borland

Bug Description

The calendar layer selection should remain in place when advancing forward/backwards, changing view (calendar/list) or changing time horizon (day/week/month). We are getting lots of complaints from users because regardless of layer selection, it reverts back to All Layers whenever you leave your current view. This makes it difficult to track a specific layer forwards and backwards without continually re-selecting the layer you want every time you advance the calendar. The calendar layer should reset when the users chooses All Layers or when the users clicks off the calendar onto a different tool.

There might be edge cases I'm not thinking of on this one, but I think we can make the user experience on this a bit cleaner.

Revision history for this message
Paul Everitt (paul-agendaless) wrote :

Right, layer selection was never meant to be a "sticky" choice. The only cases where we have sticky choices in KARL are places where there is only one of those in all of KARL.

Most likely you want the choice a user makes to be separately-sticky choice, for each calendar in KARL. That's a new area for us. We can't really treat that like a bug, and need to put that through our feature process.

Revision history for this message
Paul Everitt (paul-agendaless) wrote :

I'll assign to Nat and leave unscheduled for now.

Changed in karl3:
assignee: nobody → Nat Katin-Borland (nborland)
Changed in karl3:
importance: Undecided → Low
milestone: none → m119
Revision history for this message
Paul Everitt (paul-agendaless) wrote :

We need to slow everything down until we get clarity on the Q4 budget.

Changed in karl3:
milestone: m119 → m120
Changed in karl3:
milestone: m120 → m123
Revision history for this message
Paul Everitt (paul-agendaless) wrote :

As noted in the comment, this needs to get scheduled via feature backlog. The fact that this is 11 months old means it's not worth tracking. Moving to the barge.

Changed in karl3:
milestone: m123 → m999
Changed in karl3:
importance: Low → Undecided
affects: karl3 → karl4
Changed in karl4:
milestone: m999 → none
Changed in karl4:
milestone: none → 003
Changed in karl4:
milestone: 003 → 999
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.