10X: Assign Team Roles

Jira Align’s team roles are designed to reflect a user’s permissions at a team level. Users can be a member of multiple teams at a time, but their responsibilities on each team may differ. Assign users team roles for each team they’re on to allow them to manage the team’s sprints as needed.

To add a member to a team and assign them a team role:

  1. Navigate to Team > Manage > Teams. The Teams grid displays.
  2. Select the team you would like to assign members to. The team slide-out menu appears with detailed information about the team.
  3. Select the Members tab to assign members to the team.
  4. In the Team Member drop-down, select the name of the Jira Align user you’d like to add to the team. You can select multiple users in the drop down as desired.
  5. Click outside the drop down to close it. The selected members are assigned to the team and appear in the Team Roles panel. 

  1. On the Team Roles panel, each team member is listed with a drop-down menu where you can select their role on the team.

    Each user’s team role reflects the member’s responsibilities for their specific team, such as running standup meetings, accepting stories, or managing sprints. For example, while a story is in the backlog, anyone can work with it. However, after the sprint starts, only certain team members can make changes. The responsibilities associated with each role are pre-set and cannot be user configured.

Depending on the type of team selected, each user can be assigned one role per team from certain types of roles:

  • Portfolio Teams: Business Owner, Enterprise Architect, or Epic Owner.

    Note:
    Portfolio team members who are assigned these roles are automatically granted access to view work for all program and Agile teams associated with the portfolio with the same rights as a stakeholder. However, they aren’t automatically listed in the program or Agile team member lists.
  • Program Teams: Release Train Engineer*, Stakeholder, or Team of Team.

    Note:
    Program team members who are associated with these roles are automatically granted access to view work for all Agile teams associated with the program with the same rights as a stakeholder. However, they aren’t automatically listed in the Agile team member lists.

  • Agile Teams: Analyst, Architect, Business Owner*, Developer, Documentation, Enterprise Owner*, Epic Owner*, Product Owner, Release Train Engineer*, QA Lead, Scrum Master, Stakeholder, Team Coach, Tester, or UX.

    Note:
    Agile team members are automatically granted access to view work for all Agile teams associated with the team’s program. However, they are they aren’t automatically listed in other Agile team member lists so that different permission levels can be set for each Agile team a user is a member of.

* Users assigned this role prior to version 10.30 will appear on the Agile team member list with the role, and will have their associated permissions. However, after changing the user's role to another role, the role cannot be re-selected as an Agile team member and must be reassigned on a portfolio or program team.

 To learn more about the permissions and abilities associated with each role, select a role below:

 

Analyst

Analysts can:

  • View work for all agile teams in a program
  • Change a story’s sprint assignment before a sprint is in progress
  • Change a story’s sprint assignment during an in-progress sprint
  • Drop stories from not started sprints
  • Drop stories from in-progress sprints
  • Copy stories
  • Split stories
  • Reassign stories to another program during in-progress sprints
  • Merge stories
  • Delete stories during not started sprints*
  • Delete stories during in-progress (unlocked) sprints**
  • Be assigned task allocation and defect allocation
  • Accept stories
  • Create tasks
  • Enter time on tasks***
  • Attend team meetings
  • Create acceptance criteria before a sprint is in progress
  • Create acceptance criteria during in-progress (unlocked) sprints
  • Create acceptance criteria during locked sprints
  • Pass/fail acceptance criteria
  • Automate acceptance criteria

* Stories created from a split cannot be deleted by an analyst.
** The story's owner, designated in the Assigned field, can delete a story that has not been created from a split during an unlocked, in-progress sprint, so long as the permissions associated with their system role allow it.
*** Tasks must be assigned to the user.

Architect

Architects can:

  • View work for all agile teams in a program
  • Change a story’s sprint assignment before a sprint is in progress
  • Copy stories
  • Merge stories
  • Delete stories during not started sprints*
  • Delete stories during in-progress (unlocked) sprints**
  • Be assigned task allocation and defect allocation
  • Create tasks
  • Enter time on tasks***
  • Attend team meetings
  • Create acceptance criteria before a sprint is in progress
  • Create acceptance criteria during in-progress (unlocked) sprints
  • Pass/fail acceptance criteria
  • Automate acceptance criteria

 * Stories created from a split cannot be deleted by an architect.
** The story's owner, designated in the Assigned field, can delete a story that has not been created from a split during an unlocked, in-progress sprint, so long as the permissions associated with their system role allow it.
*** Tasks must be assigned to the user.

Business Owner

Users assigned this role prior to version 10.30 will appear on the Agile team member list with this role, and will have their associated permissions. However, after changing a member’s role to another role, the role cannot be re-selected as an Agile team member and must be reassigned on a portfolio team.

 Business owners can:

  • View work for all agile teams in a program
  • Change a story’s sprint assignment before a sprint is in progress
  • Copy stories
  • Merge stories
  • Delete stories from not started sprints*
  • Create tasks
  • Enter time on tasks**
  • Attend team meetings
  • Create acceptance criteria before a sprint is in progress

 * Stories created from a split cannot be deleted by a business owner.
** Tasks must be assigned to the user.

Developer

Developers can:

  • View work for all Agile teams in a program
  • Change a story’s sprint assignment before a sprint is in progress
  • Copy stories
  • Merge stories
  • Delete stories from not started sprints*
  • Delete stories from in-progress (unlocked) sprints**
  • Be assigned task allocation and defect allocation
  • Create tasks
  • Enter time on tasks***
  • Attend team meetings
  • Create acceptance criteria before a sprint is in progress
  • Create acceptance criteria during in-progress (unlocked) sprints
  • Pass/fail acceptance criteria
  • Automate acceptance criteria

* Stories created from a split cannot be deleted by a developer.
** The story's owner, designated in the Assigned field, can delete a story that has not been created from a split during an unlocked, in-progress sprint, so long as the permissions associated with their system role allow it.
*** Tasks must be assigned to the user.

Documentation

Documentation can:

  • View work for all agile teams in a program
  • Change a story’s sprint assignment before a sprint is in progress
  • Copy stories
  • Merge stories
  • Delete stories from not started sprints*
  • Delete stories from in-progress (unlocked) sprints**
  • Be assigned task allocation and defect allocation
  • Create tasks
  • Enter time on tasks***
  • Attend team meetings
  • Create acceptance criteria before a sprint is in progress
  • Create acceptance criteria during in-progress (unlocked) sprints

* Stories created from a split cannot be deleted by documentation.
** The story's owner, designated in the Assigned field, can delete a story that has not been created from a split during an unlocked, in-progress sprint, so long as the permissions associated with their system role allow it.
*** Tasks must be assigned to the user.

Enterprise Architect

Users assigned this role prior to version 10.30 will appear on the Agile team member list with this role, and will have their associated permissions. However, after changing a member’s role to another role, the role cannot be re-selected as an Agile team member and must be reassigned on a portfolio team.

Enterprise Architects can:

  • View work for all agile teams in a program
  • Change a story’s sprint assignment before a sprint is in progress
  • Copy stories
  • Merge stories
  • Delete stories from not started sprints*
  • Create tasks
  • Enter time on tasks**
  • Attend team meetings
  • Create acceptance criteria before a sprint is in progress

 * Stories created from a split cannot be deleted by an enterprise architect.
** Tasks must be assigned to the user.

Epic Owner

Users assigned this role prior to version 10.30 will appear on the Agile team member list with this role, and will have their associated permissions. However, after changing a member’s role to another role, the role cannot be re-selected as an Agile team member and must be reassigned on a portfolio team.

Epic Owners can:

  • View work for all Agile teams in a program
  • Change a story’s sprint assignment before a sprint is in progress
  • Copy stories
  • Merge stories
  • Delete stories from not started sprints*
  • Create tasks
  • Enter time on tasks**
  • Attend team meetings
  • Create acceptance criteria before a sprint is in progress

 * Stories created from a split cannot be deleted by an epic owner.
** Tasks must be assigned to the user.

Product Owner

Product Owners can:

  • View work for all agile teams in a program
  • Change a story’s sprint assignment before a sprint is in progress
  • Change a story’s feature assignment when a sprint is not completed*
  • Drop stories from not started sprints
  • Drop stories from in-progress sprints
  • Copy stories
  • Split stories
  • Reassign stories to another program during in-progress sprints
  • Merge stories
  • Delete stories during not started sprints**
  • Delete stories during in-progress (unlocked) sprints***
  • Accept stories
  • Create tasks
  • Enter time on tasks****
  • Attend team meetings
  • Update an In Development sprint state
  • Create acceptance criteria before a sprint is in progress
  • Create acceptance criteria during in-progress (unlocked) sprints
  • Pass/fail acceptance criteria
  • Automate acceptance criteria

After a sprint is completed, only users with the Super Admin system role can change a story’s feature assignment.
**Stories created from a split cannot be deleted by a product owner.
*** The story's owner, designated in the Assigned field, can delete a story that has not been created from a split during an unlocked, in-progress sprint, so long as the permissions associated with their system role allow it.
**** Tasks must be assigned to the user.

QA Lead

QA Leads can:

  • View work for all agile teams in a program
  • Change a story’s sprint assignment before a sprint is in progress
  • Copy stories
  • Merge stories
  • Delete stories from not started sprints*
  • Delete stories from in-progress (unlocked) sprints**
  • Be assigned task allocation and defect allocation
  • Create tasks
  • Enter time on tasks***
  • Attend team meetings
  • Create acceptance criteria before a sprint is in progress
  • Create acceptance criteria during in-progress (unlocked) sprints
  • Pass/fail acceptance criteria
  • Automate acceptance criteria

* Stories created from a split cannot be deleted by a QA lead.
** The story's owner, designated in the Assigned field, can delete a story that has not been created from a split during an unlocked, in-progress sprint, so long as the permissions associated with their system role allow it.
*** Tasks must be assigned to the user.

Release Train Engineer (RTE)

RTEs can:

  • View work for all agile teams in a program
  • Change a story’s sprint assignment before a sprint is in progress
  • Copy stories
  • Merge stories
  • Delete stories from not started sprints*
  • Create tasks
  • Enter time on tasks**
  • Attend team meetings
  • Create acceptance criteria before a sprint is in progress

* Stories created from a split cannot be deleted by a RTE.
** Tasks must be assigned to the user.

Scrum Master

Scrum Masters can:

  • View work for all Agile teams in a program
  • Change a story’s sprint assignment before a sprint is in progress
  • Change a story’s sprint assignment during an in-progress sprint
  • Change a story’s feature assignment when a sprint is not completed*
  • Drop stories from not started sprints
  • Drop stories from in-progress sprints
  • Copy stories
  • Split stories
  • Reassign stories to another program during in-progress sprints
  • Merge stories
  • Delete stories during not started sprints**
  • Delete stories during in-progress (unlocked) sprints***
  • Be assigned task allocation and defect allocation
  • Create tasks
  • Enter time on tasks****
  • Attend team meetings
  • Update an In Development sprint state
  • Create acceptance criteria before a sprint is in progress
  • Create acceptance criteria during in-progress (unlocked) sprints
  • Create acceptance criteria during locked sprints
  • Pass/fail acceptance criteria
  • Automate acceptance criteria

*After a sprint is completed, only users with the Super Admin system role can change a story’s feature assignment.
** Stories created from a split cannot be deleted by a scrum master.
*** The story's owner, designated in the Assigned field, can delete a story that has not been created from a split during an unlocked, in-progress sprint, so long as the permissions associated with their system role allow it.
**** Tasks must be assigned to the user.

Stakeholders

Stakeholders can:

  • View work for all agile teams in a program
  • Change a story’s sprint assignment before a sprint is in progress
  • Copy stories
  • Merge stories
  • Delete stories from not started sprints*
  • Create tasks
  • Enter time on tasks**
  • Attend team meetings
  • Create acceptance criteria before a sprint is in progress 

* Stories created from a split cannot be deleted by a stakeholder.
** Tasks must be assigned to the user.

Team Coach

Team Coaches can:

  • View work for all Agile teams in a program
  • Change a story’s sprint assignment before a sprint is in progress
  • Change a story’s sprint assignment during an in-progress sprint
  • Change a story’s feature assignment when a sprint is not completed*
  • Drop stories from not started sprints
  • Drop stories from in-progress sprints
  • Copy stories
  • Split stories
  • Reassign stories to another program during in-progress sprints
  • Merge stories
  • Delete stories during not started sprints
  • Delete stories during in-progress (unlocked) sprints**
  • Delete stories during locked sprints
  • Create tasks
  • Enter time on tasks***
  • Attend team meetings
  • Update an In Development sprint state
  • Create acceptance criteria before a sprint is in progress
  • Create acceptance criteria during in-progress (unlocked) sprints
  • Create acceptance criteria during locked sprints
  • Pass/fail acceptance criteria
  • Automate acceptance criteria

* After a sprint is completed, only users with the Super Admin system role can change a story’s feature assignment.
** The story's owner, designated in the Assigned field, can delete a story that has not been created from a split during an unlocked, in-progress sprint, so long as the permissions associated with their system role allow it.
*** Tasks must be assigned to the user.

Tester

 Testers can:

  • View work for all Agile teams in a program
  • Change a story’s sprint assignment before a sprint is in progress
  • Copy stories
  • Merge stories
  • Delete stories from not started sprints*
  • Delete stories from in-progress (unlocked) sprints**
  • Be assigned task allocation and defect allocation
  • Create tasks
  • Enter time on tasks***
  • Attend team meetings
  • Create acceptance criteria before a sprint is in progress
  • Create acceptance criteria during in-progress (unlocked) sprints

* Stories created from a split cannot be deleted by a tester.
** The story's owner, designated in the Assigned field, can delete a story that has not been created from a split during an unlocked, in-progress sprint, so long as the permissions associated with their system role allow it.
*** Tasks must be assigned to the user.

UX

UX can:

  • View work for all Agile teams in a program
  • Change a story’s sprint assignment before a sprint is in progress
  • Copy stories
  • Merge stories
  • Delete stories from not started sprints*
  • Delete stories from in-progress (unlocked) sprints**
  • Be assigned task allocation and defect allocation
  • Create tasks
  • Enter time on tasks***
  • Attend team meetings
  • Create acceptance criteria before a sprint is in progress
  • Create acceptance criteria during in-progress (unlocked) sprints
  • Pass/fail acceptance criteria
  • Automate acceptance criteria

* Stories created from a split cannot be deleted by UX.

** The story's owner, designated in the Assigned field, can delete a story that has not been created from a split during an unlocked, in-progress sprint, so long as the permissions associated with their system role allow it.
*** Tasks must be assigned to the user.

Notes:

  • While the rights and responsibilities for each team role cannot be configured, an individual user’s responsibilities may be limited based on their Jira Align system role, regardless of their team role assignment. For example, if a user is assigned the product owner team role, but cannot accept stories as a part of their system role, they won’t be able to accept stories for the team.

    Likewise, with the exception of users assigned the Super Admin system role, users who are not assigned to a team won’t be able to perform the responsibilities listed above for the team.

  • If a team member impersonates another team member with another role that has reduced responsibilities, the impersonating user will be able to execute the responsibility as though they had their original role with the larger responsibilities. For example, if a user with the product owner role impersonates a stakeholder on the same team, they’d still be able to see the option to change a story’s sprint assignment while a sprint is in progress as though they were a product owner.

Was this article helpful?
0 out of 0 found this helpful
Print Friendly Version of this pagePrint Get a PDF version of this webpagePDF

Join the Atlassian Community!

The Atlassian Community is a unique, highly collaborative space where customers and Atlassians come together. Ask questions and get answers, start discussions, and collaborate with thousands of other Jira Align customers. Visit the Jira Align Community Collection today.

Need to contact Jira Align Support? Please open a support request.