You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
With the changes made to AR, i.e. skills and working hours no longer being relevant, I assume the only value of a team in AR, shared or otherwise, is to assign work, sort issues and of course to measure team velocity - nothing more granular than that?
If this is the case, is there any point in populating the members of an AR team except as a reference to who is on the team?
Hi @Rafe Nussey ,
Your assumption is correct adding members to a team is mostly used for reference. If you need to plan team capacity when people join, leave, or on holiday you can adjust the capacity in the sprint/iteration flyout. Details how to can be found here.
I hope that helps,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.