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

Laszlo Kremer
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
August 1, 2012

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

2 answers

1 accepted

0 votes
Answer accepted
Laszlo Kremer
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
January 10, 2013

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.

0 votes
boardtc
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
November 13, 2012

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