Bug 1042108

Summary: [RFE][horizon]: Make navigation sticky per user account so that the sections in each tab a user navigates to is remembered.
Product: Red Hat OpenStack Reporter: RHOS Integration <rhos-integ>
Component: RFEsAssignee: RHOS Maint <rhos-maint>
Status: CLOSED UPSTREAM QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: markmc, yeylon
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
URL: https://blueprints.launchpad.net/horizon/+spec/sticky-navigation
Whiteboard: upstream_milestone_none upstream_status_unknown upstream_definition_superseded
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-19 17:04:27 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description RHOS Integration 2013-12-12 20:58:46 UTC
Cloned from launchpad blueprint https://blueprints.launchpad.net/horizon/+spec/sticky-navigation.

Description:

The goal behind this feature would be for the navigation to act in a sticky way per user account. If a user were to log in and navigation to a specific section, the application would remember this so that they next time they log in, the user will be taken to the last section they were looking at. This feature would also remember which secondary section a user was at in each primary section. For example, if the user was looking at the Volumes section in the "Projects" tab and they move over to the "Admin" tab, whenever they choose to come back to the "Projects" tab, the application remembers that Volumes was the last section that they were looking at in the "Projects" section, so the user is taken directly there.

The idea here is to avoid clicks that aren't necessary for the user to make if they bounce between primary sections a lot. This feature will be much more powerful to users as we update the navigation and scale out to more primary sections as the application continues to grow.

Specification URL (additional information):

None