What is the recommended number of "Issues per page" on Planning board?

Raising this number above 100-200 at several users could cause performance issues?

2 answers

1 accepted

0 votes
Accepted answer

The project has a few thousands issues, and 20+ unreleased fixversions. It turned out that the total number of unarchived fixversions can cause problem: if you only release them they disappear from the interface but slowness remains regardless of the number of visible issues.

It turned out also that the healthy amount of issues are about 100.

It is down to trial and error on your behalf to see how rendering is effected v #issues. I like to see all the issus on one page.

How long are your sprints and how big is your team? Reducing both wil mean less issues, you should have a manageable amount for each sprint. If not you mean need to look at reducing both of these.

Suggest an answer

Log in or Sign up to answer
Community showcase
Asked Thursday in Jira Ops

I'm John Allspaw, Ask Me Anything about incident analysis and postmortems

I'm John Allspaw, co-founder of   Adaptive Capacity Labs, where we help teams use their incidents to learn and improve. We bring research-driven methods and approaches to drive effective inciden...

464 views 2 5
View question

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you