Highlighted
Absent Member.. Wade Walden Absent Member..
Absent Member..
84 views

In Requirements, 'Author' can't move(cut&paste) requirement items from one folder to another.

In Requirements, 'Author' can't move(cut&paste) requirement items from one folder to another.

Issue:
In project 'Service_Validation_and-Testing', as Engineer and Engineer2 in Requirements, the 'Author' is not able to 'Move' or 'Cut&Paste' a requirement they created, from one folder to another.  Even though under
Groups and permissions > permissions > requirements > requirement > move > by owner only is checked.

Please advise, thank you.

0 Likes
3 Replies
Tuan_Nguyen_QC Honored Contributor.
Honored Contributor.

Re: In Requirements, 'Author' can't move(cut&paste) requirement items from one folder to another

Hi Wide,

Thank for your question.

Can you share screenshot for permissions setting in Req?

Thanks,

Tuan

"Micro Focus Support
If you find this or or any post resolves your issue, please be sure to mark it as an accepted solution and give KUDOS to the author for their assistance."
0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

Re: In Requirements, 'Author' can't move(cut&paste) requirement items from one folder to another

I can repeat that problem in QC 12.01. Obviously a bug.

Jan Czajkowski

[Please do not contact me off line for receiving support. Use the forum!]
0 Likes
Micro Focus Expert
Micro Focus Expert

Re: In Requirements, 'Author' can't move(cut&paste) requirement items from one folder to another

I've had this exact issue on several projects, others not, so I can't identify root cause. Adjusting group permissions doesn't fix the issue; not sure why.

There is a fix but you must be careful.

1) Issue the following queries to your project database/schema...

select * from groups
select * from actions where ac_action_name = 'ac_move_requirement'

2) For the first query, from the GROUPS table, note the number of records, keep the results up as a reference

3) On the second query focus on the field AC_GRANT_MASK. It is a bit-mask. Make note of the current value accurately as this is your back-out plan.

The order in which the groups appear in the first query corresponds to each digit in the bit-mask.

For example...

0	TDAdmin
1	QATester
2	Project Manager
3	Developer
4	Viewer
1053	Model Manager
1059	ALM_Perms

AC_GRANT_MASK = 1110011
Digit 1 (1) - TDAdmin can move
Digit 2 (1) - QATester can move
Digit 3 (1) - Project Manger can move
Digit 4 (0) - Deverloper can not move
Digit 5 (0) - Viewer can not move
Digit 6 (1) - Model Manager can move
Digit 7 (1) - ALM_Perms can move

If we want the Viewer group to be able to move the req we must update the AC_GRANT_MASK based on the group's position in the bit-mask. For Viewer group this is digit 5. Therefore the AC_GRANT_MASK will change from "1110011" to "1110111".

We involke using this query...

update actions set ac_grant_mask = 1110111 where ac_action_name = 'ac_move_requirement'

Once this is complete either bounce the ALM service or remove/restore the project in the Site Administration to refresh cache.

Mind that if something flies off the rails change the bit-mask value back to what it was (Step 3).

Phil Trostel
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.