A fix is available
APAR status
Closed as program error.
Error description
Only the owner of a Change Proposal System (CPS) group can remove a Change Proposal (CP) from that group. However, other users can add CPs to the groups owned by someone else. Also, Using DOORS says the CP Reviewer should be able to remove CPs from groups, but that is not the case, if the group owner is some other user (test details included below). Step 7 of Using DOORS, p. 326 (p. 344 of PDF): --- If you are a member of the change proposal review team and you want to add the change proposal to a group: a.Click Add to Group. b.Navigate to the group to which you want to add the change proposal by clicking Search up or Search down. c.Select the group you want and click Select. Note If you add the change proposal to a master group, the change proposal becomes a slave of that group, and its status is changed to the status of the master. The Status list is no longer available because slave change proposals inherit their status from the master group. You can remove the change proposal from the group by clicking Remove. --- The following tests demonstrate the discrepancy between the documented behavior and the actual behavior. Test 1: - Log in as a DOORS user of type Database Manager. - Create a new project and then create a new module in that project. - Create a new CPS for the project. - If needed, create 2 Standard DOORS users, say userA and userB. These users will have the Standard CPS role. - If needed, create a third Standard DOORS user that will have the CP Reviewer role, say reviewer. Be sure to check the checkbox that allows the CP Reviewer to edit CPs. - Log in as userA and submit a CP. - As userA, access Manage Groups and create a new group of type Master. - As userA, try to add the new CP to the new group. This works. - As userA, try to remove the CP from the group. This works. - As userA, close all your open modules. - Log in as userB. - As userB, open the module in the test project. - As userB, submit a new CP and add it to the group created by userA during the CP creation process. - As userB, try to remove the CP you just created from the group. This does NOT work because the Remove command is grayed out. Test 2: - Log out of DOORS as all other users, and log in as reviewer. - Open the module with the CPs and start the review process. - Go through all the CPs -- the Remove button is grayed out in all of them, even though it should be available in all of them per the doc. The second test demonstrates the discrepancy between the documented behavior and the actual behavior. Per the doc, the CP Reviewer should be able to add/remove CPs from any group -- see step 7 of Using DOORS, p. 326 (p. 344 of PDF). Both tests indicate that DOORS is preventing users from removing groups from sections that do not correspond to their user ID, even though these users can add CPs to these sections.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * **************************************************************** * PROBLEM DESCRIPTION: * **************************************************************** * RECOMMENDATION: * **************************************************************** Only the owner of a Change Proposal System (CPS) group can remove a Change Proposal (CP) from that group. However, other users can add CPs to the groups owned by someone else. Also standard user is allowed to remove change proposal from the group they own
Problem conclusion
Standard user must not be allowed to remove Change Proposals from the group. Hence the behavior is altered to suit the requirements CP Manager or CP Reviewer, who is the owner of the group can remove Change Proposals under the group they respectively own. However, standard user is not allowed to remove a CP from the group. For a group created by Standard user, CPM/CPR for that CPS will be allowed to remove the change Proposal, provided logged user has no standard role for the selected CP's CPS Solution in steps: 1. Group owner CPM/CPR 2. Logged user is the owner 3. Enable Remove button 1. Group owner Standard user 2. Logged in user non owner and non Standard user 3. Enable Remove button
Temporary fix
Comments
APAR Information
APAR number
PM43909
Reported component name
TLOGIC DOORS
Reported component ID
5724V61DR
Reported release
920
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-07-18
Closed date
2012-03-09
Last modified date
2012-03-09
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
TLOGIC DOORS
Fixed component ID
5724V61DR
Applicable component levels
R920 PSN
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSYQBZ","label":"Rational DOORS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.2","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]
Document Information
Modified date:
27 October 2021