Does JIRA Software (Cloud) have a limit on the number of issues that show up on the Kanban Board?

[Ross Dammann]

Jira core cloud has a limit of 1000 issues. We have over 5000 issues spread over 25 people. We want people to click 'Assign to Me' and have it show their issues. But if its not part of the first 1000, then it doesn't show them.

This is a big issue for us.

[Daniel Wester]

You might want to add in a sub filter ( https://confluence.atlassian.com/jirasoftwarecloud/configuring-filters-764477988.html#Configuringfilters-(Kanbanonly)Addingasub-filter ). 200 assigned issues per person is a lot - not quite sure that a board would be the best way for folks to find things that way.  Perhaps filter out the done issues?

[Ross Dammann]

Thanks Daniel. Is this for Jira Software only or Jira Core Cloud? We function as a contract & grant department, where we can have as many as 100 grant proposals per person reviewing at a time.

[somethingblue]

Hi Ross,

This is for JIRA Server as well.  There was a Suggestion open to make this editable by the admin but it was Closed as Won't do.  You can find it at JRASERVER-25493.

Cheers,

Branden

[Daniel Wester]

my suggestion would to look into alternative ways. If you think of the boards of being physical sticky notes on a wall - 5000 stickies would be a lot - 200 is a lot for a single person to keep track of. 

You may want to look into perhaps using filters and have people work from a list? Boards really work when they’re actionable for the entire team. 

[Ross Dammann]

Thanks Daniel. I would agree with your statement. There are probably 15-20 they are 'actively working on'. another 40-60 that are missing small amounts of information for them to consider it done. These 'done' issues are issues they will want to retrieve later. I agree they don't need to be on the board, but need to be accessible. Also oftentimes, these 'inactive' issues are updated with new information from another system. Basically, we are doing an ETL from one system to JIRA daily. Downloading the issues in JIRA, matching them with data from another system, then importing again into JIRA. Sounds crazy, but can't think of another way.