Bug 953989
| Summary: | PRD33 - Events main tab / sub-tabs Must Support the UI Plug-in Model | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Keith Robertson <kroberts> | ||||
| Component: | RFEs | Assignee: | Vojtech Szocs <vszocs> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Jiri Belka <jbelka> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 3.2.0 | CC: | abaron, aburden, acathrow, adahms, ecohen, iheim, jmoran, jwest, lpeer, lyarwood, pstehlik, sshumake, vszocs | ||||
| Target Milestone: | --- | Keywords: | FutureFeature | ||||
| Target Release: | 3.3.0 | ||||||
| Hardware: | All | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | ux | ||||||
| Fixed In Version: | is4 | Doc Type: | Enhancement | ||||
| Doc Text: |
Previously, the user interface plug-in API did not support integration with the main Events tab and its individual sub-tabs, both of which are standard tab types in the Administration Portal. This resulted in user interface plug-ins being unable to use 'add action button' functionality for these tab types, including context-sensitive buttons located in the action panel of the main tab and sub-tabs and context-sensitive menu items triggered by right-clicking the main tab or sub-tabs. With this update, the plug-in API has been updated to enable 'add action button' for the above tabs, allowing user interface plug-ins to integrate with the Events tab and its sub-tabs via the action button concept.
|
Story Points: | --- | ||||
| Clone Of: | |||||||
| : | 975673 (view as bug list) | Environment: | |||||
| Last Closed: | 2014-01-21 17:17:57 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 894399, 975673, 978804, 1019470 | ||||||
| Attachments: |
|
||||||
|
Description
Keith Robertson
2013-04-19 19:33:05 UTC
I assume this is about adding custom context-sensitive buttons/menu-items to existing Event-related tab(s).
Currently, we have addMainTabActionButton API function for main tabs. Currently, this API function doesn't support "Events" main tab, this RFE is intended to add support for this main tab:
api.addMainTabActionButton('Event', 'Button/menu-item label', {
...
onClick: function() { ... },
isEnabled: function() { ... },
...
});
Keith, do we also need to support adding custom context-sensitive buttons/menu-items to existing Event-related *sub* tabs? If the answer is yes, we'll have to introduce new API function for this purpose:
// Add action button to Cluster Event sub-tab
api.addSubTabActionButton('Cluster', 'Event', 'Button/menu-item label', { ... });
We would like to be able to add Action buttons in both main-tabs and sub-tabs. Anywhere the user can access events, there will be value added by being able to "Diagnose" the event using our services. Thanks Spenser, so we will need to improve existing addMainTabActionButton API + add new addSubTabActionButton API. Both API functions should support all table-based main/sub tabs. Created attachment 762102 [details]
Test UI Plugin
A plugin that verifies addSubTab, addMainTabActionButton and addSubTabActionButton API functions.
ok, is6. This bug is currently attached to errata RHEA-2013:15231. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag. Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information: * Cause: What actions or circumstances cause this bug to present. * Consequence: What happens when the bug presents. * Fix: What was done to fix the bug. * Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore') Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug. For further details on the Cause, Consequence, Fix, Result format please refer to: https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes Thanks in advance. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2014-0038.html |