When you build out your team hierarchy, you will come across two types of hierarchy elements: teams and team lines.
Teams should be organized around what you deliver to your customers or users.
Team lines are a way for you to organize your teams into families, suites, or groups. Team lines can also represent any level in your organization, such as business units, divisions, or Scaled Agile Framework (SAFe) agile release trains. Therefore, a team line can contain other team lines and team.
You must be an administrator with customization permissions to configure teams and team lines.
Click any of the following links to skip ahead:
Configure your team hierarchy
Setting the right hierarchy is important if you want easy navigation or to set up more sophisticated user permissions.
You can start by setting up either teams or team lines under Settings ⚙️ -> Account -> Teams. You can rearrange your groupings at any time. You can adjust your team hierarchy by creating a team line and then selecting which teams belong to it. Or you can select a team and choose which team line it belongs to.
Teams cannot be converted to team lines and vice versa.
Configure teams
Click Add team.
Select the team line your new team should belong to (if one exists).The Team line field shows where your team line fits into the hierarchy — specifically who a team line's parents are in the hierarchy. This field is optional since a team line might not have any parents.
Name your team. The Name field is the name you would like to display throughout Aha! reports and records.
Add a prefix. Aha! records use the Prefix field to build unique identifiers for records in that team line. The abbreviation you pick here should be a good shorthand for the team line. You can edit it, but editing the prefix will not change any records created with the original prefix.
Configure team lines
Click on Add line.
Select the team line your new line belongs to (if one exists).
Enter a Name, Prefix, and Label.
Add any child teams or team lines (if they exist). Then click Create line.
A team line also inherits its terminology in the top-level navigation menu from its label.
It may be helpful to select consistent team line label nomenclature across your Aha! account before you start creating team lines. (For example: "Company -> Division -> Subdivision -> Team" or "Organization -> Unit -> Group -> Team.") You can also edit this field at any time if your account's nomenclature needs to change.
There are situations where you might want to have inconsistent nomenclature in your account — if you want to ensure that no one will be able to accidentally report on one team's work under a different team line's epics, for example.
Remember that once you create a team hierarchy, you can select which team or team line you are going to work on from the dropdown menu at the top-left of the Aha! Develop navigation.
This dropdown allows you to expand or collapse team lines, type to search for a specific team, and also saves the three most recent teams you have viewed for faster access.
Move teams to a new team line
If your team hierarchy changes, you may need to move a team or a set of teams to a new team line. Before you do so, consider the ways the move might affect your team:
Many team settings can be inherited from the team line — which means moving a team to a new team line will also change the team's settings.
Users can inherit their user permissions from a team line — which means moving a team to a new team line could also change users' team access and permission levels.
To address these concerns, review the settings of the team(s) you intend to move. Pay attention to any setting that is set to Inherit from line, and make sure the new team line's settings are settings you want the child team to inherit.
Then, it is time to look at users. Navigate to Settings ⚙️ -> Account -> Users and filter the list of users by the team(s) you intend to move. Make sure that the appropriate users have the appropriate user permissions in the new team line.
Settings that will not move with the team if set to inherit from the old team line |
Account settings Team settings |
Settings that will move along with the team to the new team line |
While moving a team to a new team line will maintain record links, users associated with that team may see their permissions change as a result of the move, and may not be able to see or access some linked records.
|
View teams and workspaces together
If you have connected Aha! Develop and Aha! Roadmaps in your Aha! account, then you will see your Aha! Develop teams in two places: as part of their team lines, and within the workspace lines they support. This makes it easier for everyone to find (and send work to) the right team.
In this screenshot, you can see the same Frontend team visible within both the workspace and team lines.
An Aha! Develop team will show up under any related Aha! Roadmaps workspace line. To relate Aha! Develop teams and Aha! Roadmaps workspaces together, navigate to Settings ⚙️ -> Team -> Aha! Roadmaps -> Configure.
Create your overall team structure
With teams and team lines, you will create an overall structure representing your offerings and how they are related to one another for your customers and within your company.
Often your teams have technical components, or are part of a bundled or larger solution, or may even be more of a platform of capabilities to benefit the entire portfolio. When you create a team structure that considers these relationships, your hierarchy within your Aha! account will be able to accurately model your real world company structure.