What role is required to manage the Backlog and Sprints in Agile module?

lreyes1
Kilo Guru

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. 

1 ACCEPTED SOLUTION

Patrick Laroch1
Giga Guru

Here is the list of the roles, not sure what is grayed out for you.

Role title [name]DescriptionContains roles
Scrum adminA 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 masterA 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
 Epicsscrum_user
 Stories 
 Sprints 
 Team Members 
Scrum product ownerUsers 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
 Themesscrum_user
 Epics 
 Stories 
 Products 
 Releases 
 Teams 
Scrum release plannerUsers 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 plannerUsers 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 creatorUsers 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 editorUsers with this role have edit access to the Story [rm_story] table.scrum_user
[scrum_story_editor] rm_scrum_task_admin
Scrum team memberUsers 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 adminScrum task administrator with access to [rm_scrum_task] table.scrum_user
[rm_scrum_task_admin] 
Scrum userBasic 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. 

View solution in original post

5 REPLIES 5

Patrick Laroch1
Giga Guru

Here is the list of the roles, not sure what is grayed out for you.

Role title [name]DescriptionContains roles
Scrum adminA 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 masterA 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
 Epicsscrum_user
 Stories 
 Sprints 
 Team Members 
Scrum product ownerUsers 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
 Themesscrum_user
 Epics 
 Stories 
 Products 
 Releases 
 Teams 
Scrum release plannerUsers 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 plannerUsers 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 creatorUsers 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 editorUsers with this role have edit access to the Story [rm_story] table.scrum_user
[scrum_story_editor] rm_scrum_task_admin
Scrum team memberUsers 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 adminScrum task administrator with access to [rm_scrum_task] table.scrum_user
[rm_scrum_task_admin] 
Scrum userBasic 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. 

Thank you so much!

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

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) ?