Closed Bug 689392 Opened 14 years ago Closed 9 years ago

Adding environment should not have element controls

Categories

(Mozilla QA Graveyard :: MozTrap, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: rbillings, Unassigned)

Details

When adding an environment in CC, there are Delete options under 'Controls' which do not relate to adding an environment. This is confusing and potentially very bad if users can accidentally delete Environment elements during an add. 1) Add an environment 2) select 'Operating System' 3) click trash can under controls [thinking it would remove the selection from your new environment] expected: OS is no longer selected actual: error message displays that OS is in use and cannot be deleted
* Clarification: replace the word 'Element' above with 'Category' - I didn't realize you could add and delete categories. It still strikes me as wrong to be able to edit these during an Add Environment flow.
A Pivotal Tracker story has been created for this Bug: http://www.pivotaltracker.com/story/show/19198265
Cameron Dawson added a comment in Pivotal Tracker: Perhaps in "creation mode" for an env profile, we ONLY should allow a user to rename and delete items they themselves created in this session (to fix errors they JUST made). Then in order to delete and edit, they need to go into an edit mode. Presumably, there are different permission levels to delineate this. In the short term, during creation, the delete icons should be removed. It's too confusing for the user to be able to delete things that may apply to other profiles during the create process.
Carl Meyer added a comment in Pivotal Tracker: eric: here's the story you were asking about today (for redoing the create-profile screen and splitting the category/element management to its own screen).
Closing MozTrap bugs
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in before you can comment on or make changes to this bug.