Description

As a developer, I'd like to have the topology diagram layout that I move around persisted since that arrangement makes more sense to me than what was computed and it is timing consuming to rebuild it each time.

Acceptance criteria

• User make adjustments to layout on topology, they leave the topology view and return, the layout is unchanged.
• User make adjustments to layout on topology, logout from cluster and close browser. User returns later with same computer, browser and logs into cluster, they see the same layout from before.
• [stretch] Like above, but user works from different computer and/or browser (it persisted server side and not just in browser storage).

Customer and end-user feedback:

During UNC usability testing:

• Users were frustrated when the topology view did not remember users’ arrangement
• Users repeatedly re-arranged the topology view and verbalized frustration as the system did not remember their prior arrangements.

  Various internal users

• Veer has requested this for some time

Exploration Results

1. GA feature, thus should be properly documented
2. GA feature, thus need to provide enablement
3. Include in what's new RHD blog and consider for improved usability blog
4. The topology graphical layout per user should be remembered for each project, in persistent storage.
5. When working on this, consult with stakeholders (PM/UX) to understand how Reset View will behave.

Acceptance Criteria

1. As a developer, when working in the topology, the graphical layout should be remembered for each project per user
   1. Saving graphical layout should include save & pan details
   2. Saving graphical layout should include the position of components in the graph
2. User make adjustments to layout on topology, they leave the topology view and return, the layout is unchanged.
3. User make adjustments to layout on topology, logout from cluster and close browser. User returns later with same computer, browser and logs into cluster, they see the same layout from before.
4. [stretch] Like above, but user works from different computer and/or browser (it persisted server side and not just in browser storage).

Design Artifacts

N/A

Slack Channel

#tmp-odc-topology

Notes

tbd