The OPS team will start using Jira to track and approve Change Requests in the OPS project. They have these workflow requirements:
✑ Requests can be approved by two individuals only.
✑ The approvers will change weekly.
Jira is connected to your corporate LDAP with Read-Only permissions.
What is the best way to structure permissions for the OPS project to support these workflow requirements?
The best way to structure permissions for the OPS project, given the specific requirements, is to create a new project role for approvers and have the Project Role (Administrators) maintain it. This approach ensures flexibility, as the approvers change weekly, and it avoids placing additional burden on Jira administrators by continuously managing new groups or requesting changes in the corporate LDAP directory. Project roles in Jira can be easily managed by project administrators, allowing quick updates in line with the changing approvers.
it should be B
B. Create a new project role for approvers and have the Project Role (Administrators) maintain it. It should be this. Creating a group just adds too much workload to the Jira administrators.