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
Next: Root
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.
Ok. There's no direct impact of increasing the number alone to 100.
But if someone uses it (adds more than 25 gadgets to a dashboard), then yes, you could well see noticeable performance issues. When a dashboard is rendered, it effectively makes a set of calls to the Jira API all the same time. Some gadgets are very simple making only one simple call, others make several. Some calls can be quite complex. If your users have 100 gadgets on a dashboard, then when they view that dashboard, there are 100 potentially very intensive things being asked all at the same time, and your server could struggle to serve them all.
I would strongly recommend not increasing the number.