Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Is there a performance impact with more than 30 teams in a Portfolio plan

Is there a performance impact, in cloud, with more than 30 teams in a Portfolio plan?

1 answer

1 accepted

1 vote
Answer accepted
Earl McCutcheon
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Mar 20, 2019

Hi Marie,

Every data point is going to add in additional overhear, so this depends on the configurations.

If you have 30 teams with 1 team member each, I would not expect any impact, however if you had 30 teams with 100 members per team I would expect some delays on content rendering as that is a lot of overhead on any action, I would also expect delays on performing a calculations for the capacity comparisons from the amount of users to sort through for availability.

With that said however, anything we can to to improve performance is always high priority if gains can be made and especially if there is a major loss in functionality form slow running queries.  How are you plan and team settings configured? with what amount of team member loading? and what kinds of delays are you seeing?


Hi Earl,

Are you able to tell us which specific components of the plan are the most performance intensive? This way, we can turn them off incrementally in terms of importance to the team.


For example:

  • Multiple custom views
  • Color coding for bars based on a custom field
  • Several teams being imported
  • Sprints for several teams being imported
  • Numerous custom fields
  • Releases

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events