This portal is to open public enhancement requests against the products and services belonging to IBM Sustainability Software. 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).
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:
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 updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
See this idea on ideas.ibm.com
There is a related workitem from foundation as the manage of process template source is on their side: 494200: Process templates have no any migration routine on upgrade or importing from previous releases. Once they complete this enhancement we may need to adopt the functionality (likely through an extension point). This is an enhancement to match with foundation's.
Testing Environment
6.0.6/6.0.6.1 upgraded from 6.0.2
Overview
Upgrading from 6.0.2 to 6.0.6/6.0.6.1 the process template source misses permissions for categories and stream/baselines:
For example, Customer defined two roles - "Test Manager" and "Project Administrator" who can, amongst others, Crate Baselines and Categories.
In the 6.0.2 exported process template:
<project-configuration>
<permissions>
<role id="project_administrator">
<project-operation id="com.ibm.rqm.planning.categorytype.save">
<action id="create"/>
</project-operation>
<project-operation id="com.ibm.rqm.config.mgmt.create.baseline">
<action id="any"/>
</project-operation>
</role>
</permissions>
After importing to 6.0.6, the permissions are missing.
When exporting the process again (without any changes), same XML process source is received.
When correcting the settings in UI and inspecting the process source (export to zip or open in Eclipse), those are now moved into the Team Area settings:
<team-configuration>
<permissions>
<role id="project_administrator">
<operation id="com.ibm.rqm.config.mgmt.baseline.save">
<action id="create"/>
</operation>
<operation id="com.ibm.rqm.planning.categorytype.save">
<action id="create"/>
</operation>
</role>
When upgrading a 6.0.2 instance to 6.0.6 same problem is observed from the existing process templates.
Categories permissions were moved to process area at: Categories should have instance-specific permissions (130284)
Configuration permissions were changed also at: Granualize stream management permissions. (127650)
This applies the same for process templates existing during the server upgrade or exported templates prior the migration and imported after migration is done. The effect is the same for process templates. We do not migrate any permission in the source.
We only do migration of the permissions on the PROJECT AREA source.
Idea priority | Medium |
Needed By | Not sure -- Just thought it was cool |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.