Suggestion: Add separate role for requirements rename

Description

A customer is requesting to be able to assign a permission for the rename. If we do it, we must do it in our administration, it can't be integrated with Confluence's permissions.

Original text

Requirements themselves are subject to change according to the processes within company and sometimes it's needed to bulk rename them because of processes requirements change and misspelling fixes.

I believe requirements rename is a routine task and it should be available for ordinary users.
Perhaps it's worth having separate role, but definitely it is not an administrative task.

Environment

None

Observations

None
Resolved

Assignee

Salmane Hmiza

Reporter

Adrien Ragot (Play SQL / Requirement Yogi)

Labels

None

Participants

None

Fix versions

Priority

Matter of months