- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-16-2023 06:05 AM
Some of the features are grayed out for me and I cannot figure out what role is required for me to fully administer my Team's backlog, sprints and all Agile module configs.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-19-2023 06:48 AM
Here is the list of the roles, not sure what is grayed out for you.
| Role title [name] | Description | Contains roles |
| Scrum admin | A scrum admin has full control on the Agile Development 2.0 application. | scrum_user |
| [scrum_admin] | rm_product_admin | |
| rm_task_admin | ||
| rm_test_admin | ||
| rm_doc_admin | ||
| rm_story_admin | ||
| rm_epic_admin | ||
| rm_releasescrum_admin | ||
| rm_sprint_admin | ||
| Scrum master | A scrum master guides team members through a sprint and serves as a sounding board for issues that arise. | scrum_sprint_planner |
| [scrum_master] | A scrum master can move stories between a release backlog and a sprint. This user can create and manage: | scrum_story_creator |
| Epics | scrum_user | |
| Stories | ||
| Sprints | ||
| Team Members | ||
| Scrum product owner | Users with this role are responsible for the business value of a project and for maintaining the product backlog. | scrum_release_planner |
| [scrum_product_owner] | A product owner can move stories between the product backlog and releases. This user can create and manage: | scrum_story_creator |
| Themes | scrum_user | |
| Epics | ||
| Stories | ||
| Products | ||
| Releases | ||
| Teams | ||
| Scrum release planner | Users with this role perform release planning activities. | scrum_user |
| [scrum_release_planner] | A release planner can create and manage: | scrum_story_creator |
| Themes | ||
| Products | ||
| Releases | ||
| Scrum sprint planner | Users with this role manage the sprint process. | scrum_user |
| [scrum_sprint_planner] | A sprint planner can create and manage: | scrum_story_creator |
| Stories | ||
| Sprints | ||
| Scrum story creator | Users with this role create the descriptive elements of a product. | rm_scrum_task_admin |
| [scrum_story_creator] | A story creator can create and manage: | scrum_user |
| Epics | ||
| Stories | ||
| Tasks | ||
| Scrum story editor | Users with this role have edit access to the Story [rm_story] table. | scrum_user |
| [scrum_story_editor] | rm_scrum_task_admin | |
| Scrum team member | Users with this role are the scrum users who work on a story in a sprint. | scrum_user |
| [scrum_team_member] | A team member can create a scrum task, perform updates to a story, and log enhancement requests or defect reports. | scrum_story_creator |
| scrum_story_editor | ||
| rm_defect_admin | ||
| rm_enhancement_admin | ||
| rm_scrum_task_admin | ||
| Scrum task admin | Scrum task administrator with access to [rm_scrum_task] table. | scrum_user |
| [rm_scrum_task_admin] | ||
| Scrum user | Basic scrum role that all other roles inherit. It confers read-only rights to the Agile Development application. | cmdb_read |
| [scrum_user] | A scrum user can view all elements of agile, but cannot create, edit, or manage records of any type. |
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-19-2023 06:48 AM
Here is the list of the roles, not sure what is grayed out for you.
| Role title [name] | Description | Contains roles |
| Scrum admin | A scrum admin has full control on the Agile Development 2.0 application. | scrum_user |
| [scrum_admin] | rm_product_admin | |
| rm_task_admin | ||
| rm_test_admin | ||
| rm_doc_admin | ||
| rm_story_admin | ||
| rm_epic_admin | ||
| rm_releasescrum_admin | ||
| rm_sprint_admin | ||
| Scrum master | A scrum master guides team members through a sprint and serves as a sounding board for issues that arise. | scrum_sprint_planner |
| [scrum_master] | A scrum master can move stories between a release backlog and a sprint. This user can create and manage: | scrum_story_creator |
| Epics | scrum_user | |
| Stories | ||
| Sprints | ||
| Team Members | ||
| Scrum product owner | Users with this role are responsible for the business value of a project and for maintaining the product backlog. | scrum_release_planner |
| [scrum_product_owner] | A product owner can move stories between the product backlog and releases. This user can create and manage: | scrum_story_creator |
| Themes | scrum_user | |
| Epics | ||
| Stories | ||
| Products | ||
| Releases | ||
| Teams | ||
| Scrum release planner | Users with this role perform release planning activities. | scrum_user |
| [scrum_release_planner] | A release planner can create and manage: | scrum_story_creator |
| Themes | ||
| Products | ||
| Releases | ||
| Scrum sprint planner | Users with this role manage the sprint process. | scrum_user |
| [scrum_sprint_planner] | A sprint planner can create and manage: | scrum_story_creator |
| Stories | ||
| Sprints | ||
| Scrum story creator | Users with this role create the descriptive elements of a product. | rm_scrum_task_admin |
| [scrum_story_creator] | A story creator can create and manage: | scrum_user |
| Epics | ||
| Stories | ||
| Tasks | ||
| Scrum story editor | Users with this role have edit access to the Story [rm_story] table. | scrum_user |
| [scrum_story_editor] | rm_scrum_task_admin | |
| Scrum team member | Users with this role are the scrum users who work on a story in a sprint. | scrum_user |
| [scrum_team_member] | A team member can create a scrum task, perform updates to a story, and log enhancement requests or defect reports. | scrum_story_creator |
| scrum_story_editor | ||
| rm_defect_admin | ||
| rm_enhancement_admin | ||
| rm_scrum_task_admin | ||
| Scrum task admin | Scrum task administrator with access to [rm_scrum_task] table. | scrum_user |
| [rm_scrum_task_admin] | ||
| Scrum user | Basic scrum role that all other roles inherit. It confers read-only rights to the Agile Development application. | cmdb_read |
| [scrum_user] | A scrum user can view all elements of agile, but cannot create, edit, or manage records of any type. |
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-27-2023 08:13 AM
Thank you so much!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-09-2023 03:41 AM
This is fantastic. There is a lot of very similar roles. Do you know what role is specifically required to use the triage board from the agile backlog? I am finding that Scrum Admin works, but I would prefer to give less access
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-06-2024 10:37 AM
Do we need to create a custom role if we want to allow to create and manage: Themes, Epics, Stories, and Releases, but NOT Products or Teams (Groups of type=Agile) ?
