Managing and using Atlassian Groups, Teams, and Assets (LTS Teams)

Atlassian Groups can only be created and populated by Jira Administrators. These are used to provide access to Atlassian licenses and can be populated from AD. Atlassian licenses are granted by adding people to the appropriate license group on the AD side. Atlassian Groups are the most powerful of these options because you can use them for licensing, project access, notification, permissions, workflows, and automations.

• If you need an Atlassian group because you have more than a handful of people that you need to allow access to your project or space, request an AD group to be synced to Atlassian daily and can be used for Atlassian groups. Indicate on the request that you are requesting the group for use in the Atlassian products (this will ensure that the synchronization with the Atlassian groups is set up properly).

‌

Atlassian Teams is a newer feature where Atlassian users can create a team and populate the members, and new functionality is being added on a daily basis which might warrant future changes to our workflow. A team dashboard is automatically created when you create a team. This dashboard will show tasks that are assigned to your team via the global team field. This field is not to be confused with Team assignment custom fields that have been implemented in a variety of projects. We are not currently using these teams for assignment or notifications, but that might be something that we investigate using in the future. For now, they can be useful for team building and they will allow people in to use the @<team> mention to mention all the members of that team in a comment.

‌

Assets LTS Team, Assets HR teams, and Switch Replacement teams are specifically being used for team assignments in the LTS, HR, and Switch Replacement Service Management projects. These teams are managed by the appropriate team leads and these are the entities that we use for team assignment. When a ticket is assigned to one of these teams, an email notification is sent to the email address identified in that assets object. Assets teams have dedicated attributes for team members, as well as an associated Atlassian group. Associating an existing Atlassian group with a team enables existing automation to mirror asset team membership with Atlassian group membership. In other words, team membership in Assets will synchronize over to the associated Atlassian group. The group can then be used in filters to search for issues assigned to anyone within the group. If no email list exists for the asset team, the Atlassian group can serve as an alternative for emailing all group members in automations and post-functions.

‌

Each project or space has permissions that should be managed by the project lead or space owner. The following global roles have been created for use in individual projects and individual people or Atlassian groups can be added to those roles for each individual project:

Jira projects
Project Lead - All permissions needed to work on a project + the ability to delete
Project Team - All permissions needed to work on a project
Read Only - Ability to read tickets and leave comments

Jira Service Management projects

Service Desk Team - All permissions needed to work on tickets in the project

Service Desk Customers - All permissions needed to be able to submit tickets to a project