Raising this number above 100-200 at several users could cause performance issues?
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.