You can group individual users into teams, which enables effort-based planning.
The concept of teams is used mainly in the Resources, Objectives, and Board modules but, since the information about the team can be stored as a label or a custom field, it can also be displayed using Gantt, Scope, or Risks module by adding it to the Column View or Card View.
You can create global teams and assign them to multiple Boxes. Once created, you can easily convert them into Box teams, which cannot be reassigned.
| Feature | Description |
|---|---|
| Team name | A team name is used to identify teams by the App's modules. It is displayed together with the Team code in the Resources, Board, and Roadmap modules to indicate the team's swimlane and the team picker's drop-down when configuring Box level teams. |
| Team code | Team code is used to identify teams by the App's modules and, when synchronized, by the Host and connected platforms. |
| Team board link | Link the team to its Jira Board to quickly switch between different views. Based on this link, the App can auto-configure the Sub-Boxes scope synchronization and create sprints on the selected Jira Agile Board. |
Team panel | The team panel contains three tabs:
|
| User name link | A list of membership periods of a user (for a given team).
|
| Membership period | Your resources can be shared across different teams in the same period of time or can be fully allocated to a single team. This issue can be addressed using the memberships and availability of the team members. |
| Availability | You can set the availability of each team member. The availability impacts the capacity, which is calculated as the difference between working hours specified in Workload plans and non-working days. |
