Bug 1027819 - [Usability] Property management is not consistent
Summary: [Usability] Property management is not consistent
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Web Console - UX
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: EAP 6.4.0
Assignee: Catherine Robson
QA Contact: Pavel Jelinek
eap-docs
URL:
Whiteboard: Usability
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-07 12:32 UTC by Jakub Cechacek
Modified: 2019-08-19 12:46 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-08-19 12:46:20 UTC
Type: Task

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker HAL-304 0 Minor Open Property management is not consistent 2017-10-09 21:36:19 UTC

Description Jakub Cechacek 2013-11-07 12:32:00 UTC 
Usually when adding property in "New Resource" wizard a default key:value pair  is generated and "inline form" is used to set the value. However when adding properties to some resource later (outside the wizard) a popup window with inputs for key and value is shown. 

From usability point of view it might be better to have property management consistent and used the first option in both cases.
Comment 1 Heiko Braun 2014-07-09 11:38:12 UTC 
In agreement with Catherine we've decided that UX issues will be tracked separately.
Comment 2 Jakub Cechacek 2014-07-21 06:21:37 UTC 
Issue moved under the UX component. 

Also moved to 6.4 as this issue is still valid for 6.3. Use ack flags to decide whether we want to go through with it or not.
Comment 3 Heiko Braun 2014-08-25 13:48:04 UTC 
It's because we do not launch windows from windows. I don't consider this a bug, nit UX problem.
Comment 4 Catherine Robson 2015-01-27 17:53:22 UTC 
Assigning to Josephine for further investigation as part of the EAP 7 design updates.
Note You need to log in before you can comment on or make changes to this bug.