|
If you were logged in you would be able to see more operations.
|
|
|
RHQ Project
RHQ-399
Created: 04/Sep/08 01:42 PM
Updated: 25/Dec/08 06:06 AM
|
|
| Component/s: |
FX - Inventory
|
| Affects Version/s: |
1.1
|
| Fix Version/s: |
None
|
|
| Resolution Date: |
25/Dec/08 06:06 AM
|
| Date of First Response: |
25/Dec/08 05:55 AM
|
| VCS Revision: |
2,545
|
|
This is an additional set of improvements that didn't make it into the first version of the wizard.
4) "expression type" drop-down always makes the first expression "resource.type.name = Apache HTTP Server", it should either be null until one is selected or it should default to the first item in the "resource type" drop-down that gets generated after selecting the appropriate plugin
5) enablement / disablement options
5a) when "resource type" drop-down is an empty list, replace it with the printed message "there are no types defined by the selected plugin"
5b) when "property names" drop-down is an empty list, replace it with the printed message "there are no properties defined by the selected type"
6) user intuitiveness - similar to, but more direct than enablement / disablement options
6a) maybe only populate the "defining plugin" / "resource type" drop-downs with elements that are known to have resource types that have properties - this would be a complete replacement for options 5a & 5b
|
|
Description
|
This is an additional set of improvements that didn't make it into the first version of the wizard.
4) "expression type" drop-down always makes the first expression "resource.type.name = Apache HTTP Server", it should either be null until one is selected or it should default to the first item in the "resource type" drop-down that gets generated after selecting the appropriate plugin
5) enablement / disablement options
5a) when "resource type" drop-down is an empty list, replace it with the printed message "there are no types defined by the selected plugin"
5b) when "property names" drop-down is an empty list, replace it with the printed message "there are no properties defined by the selected type"
6) user intuitiveness - similar to, but more direct than enablement / disablement options
6a) maybe only populate the "defining plugin" / "resource type" drop-downs with elements that are known to have resource types that have properties - this would be a complete replacement for options 5a & 5b |
Show » |
|
Sub-task
Resolved
Minor
example for 5a) Resource > Resource Type > Database > "None defined for selected plugin" > "No type selected"
example for 5b) Resource > Resource Type > Apache > Apache HTTP Server > "None defined for selected type"