How can I see more than 250 issues in list view?

[Ben Weisman]

Other people have their pagination set to 1,000. Mine is 250. What gives?

Thanks.

[Joseph Chung Yin]

@Ben Weisman -

Are you referring to number of issues listed in JQL result page/Issue Navigator page?  If so, it is control via System/User Default Settings's Number of Issues displayed per Issue navigator page option.

I am not aware that users can override this default.  In addition, when you refer to "Other people" - Are those people users within your own systems?

Hope this helps.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Infrastructure Applications Team

Viasat Inc.

[Jack Brickey]

Agree. AFAIK this is not configurable in Cloud. I would be interested in finding out different so please share information about these other individuals. Also you mentioned 250. Mine is set at 50 and it was my understanding that was the limit.

[Joseph Chung Yin]

@Jack Brickey -

Our Cloud env is defaulted to 50 too.

One can change the system level default from 50 to other numbers.

Best, Joseph

[Jack Brickey]

Awesome @Joseph Chung Yin ! I haven't been in those settings so long I had forgotten what was there. :-)

so I tested changing it to 1000 and man that was a big performance yet. It took 3 to 4 times longer to load 1000 issues than 50. I'll stick with 50 ;-)

[Joseph Chung Yin]

@Jack Brickey -

That is why we also sticked with the 50 issues default for performance reason.  In my opinion, if I have a listing of issues of 50 or more, it is very difficult for myself to focus on which exact issues that I am trying to conduct analysis further.  In this case, less IS MORE. :)

Best, Joseph

[Paul Hawkins]

I suspect performance is the real issue here.

Having a list of more than 50 is not difficult to focus on.  That is what a scroll wheel  and column sorting is for.  Having to click a 'Next' or 'Prev' button is more disruptive to an analysis of a long list.

@Jack Brickey  Note in System this setting is under 'User Default Settings' with a opening text of:

"Set the default values for user preferences. If the user has not specified a preference then the values for the user will fall back to the default values set here. You can 'Apply' the email preference which will allow you to force each users value to be that of the default."

The solid implication is this is a default the user can change in their personal preference.  I think you are correct that is can not be changed by the user.  Thus not a default.

(thus a bug; and you thought you would not have to deal with another hawkman bug ;-) )

[Jack Brickey]

😂....oh noooooooo!