Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 388930

Summary: Comments on the User Profile update command
Product: [ECD] Orion Reporter: Maciej Bendkowski <maciej.bendkowski>
Component: ClientAssignee: Anton McConville <antonm>
Status: RESOLVED WONTFIX QA Contact:
Severity: normal    
Priority: P3 CC: antonm, maciej.bendkowski, malgorzata.tomczyk, simon_kaegi, Szymon.Brandys
Version: unspecified   
Target Milestone: 4.0 M1   
Hardware: PC   
OS: Windows 7   
Whiteboard:

Description Maciej Bendkowski CLA 2012-09-06 07:53:25 EDT 
After bug 388917, comment 1:

Two "Update" actions on User Profile may be confusing. I think we need one global update at the top of the page that affect all sections of User Profile. Moreover we need an indicator that something is unsaved. For instance changes to the name, address etc. as well as enabling Key Storage needs saving. Adding an OpenId provider removing a key does not.
Comment 1 Malgorzata Janczarska CLA 2012-09-18 09:00:52 EDT 
Anton, I talked to Maciek about how can we solve this problem. Maciek's proposition is to combine the functionality of updating the user profile and git credentials storage in one user button on the top of the page. This would follow the current strategy: one update button per one preference page.
I was however thinking on something else: right now we have only one general preference that we are editing in the Git Credential Storage section and it's enabling the storage. Other items in the storage have their own commands. I think we could get rid of the "Update" button in this section and replace it with "Enable Storage" or "Disable Storage" button. Even providing that we have plans for extending the storage on storing passwords I think we won't be needing the "Update" button for this section.
What do you think be the most consistent way to solve this problem?
Comment 2 John Arthorne CLA 2015-05-05 16:21:31 EDT 
Closing as part of a mass clean up of inactive bugs. Please reopen if this problem still occurs or is relevant to you. For more details see:


https://dev.eclipse.org/mhonarc/lists/orion-dev/msg03444.html