This is an IBM Automation portal for Cloud Platform products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
The Cadence/ClearCase integration should get comprehensive reporting facilities. This is to make changes easily visible and traceable for all developers - rather than ClearCase experts only that would need to compose complex "cleartool find" commands. Users need a reporting capability readily available in their GUI (i.e.: Library Manager and/or ClearCase Workarea Manager).
We propose to enhance the "Manage Hierarchy" and "Workarea Manager" graphical user interfaces so users will be able to create reports, which would be displayed in a tabular format, and can also be saved to text files (comma-separated values).
Scope of action: * selected elements (select, context menu): a cellview, a set of cellviews, a cell, a set of cells, a library, a set of libraries; or: all libraries visible in WAM * for individual cellview: allow to recurse the hierarchy (like in "Manage Hierarchy"
Compare (find elements): * Current view (according to rules in config spec) vs. a given label * Current view (according to rules in config spec) vs time rule (note: time on same branch only) * Current view (according to rules in config spec) vs another view * one label vs another label (find elements, which have both labels) * Time vs time (find elements, which changed between two the given time stamps - i.e. have different versions (on one branch)
For user the interaction for creating a report should be similar as. e.g. applying a label: * Define scope (selection, optionally including hierarchy) * Define "left hand side" (label, time, view) * Define "right hand side" (label, time, view) * Launch the report generation
Report should list a list of OpenAccess elements, which: * Fit the criteria (scope) and are actually different * columns for "left" version and "right" version * From the list it should be possible to apply the "usual actions": (label, checkout, checkin, uncheckout, history)
Do not place IBM confidential, company confidential, or personal information into any field.