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

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 Join to answer
Community showcase
Teodora [Botron]
Published Thursday in Marketplace Apps

Jira Inferno: The Nine Circles of Jira Administration Hell

If you spend enough time as a Jira admin - whether you are managing a single, mid-sized instance, a large enterprise one or juggling multiple instances at once - you will eventually find yourself in ...

857 views 5 18
Read article

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
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot