Is there a limit on the number of issues on a kanban board in JIRA Software like there is with Jira core cloud (1000)?
Yes, from memory, it's 3,000, or "roughly 15 times what most humans can usefully parse on a board".
A board really should not have more than a couple of hundred. If you've got thousands of issues, that's fine, but split them up into usefully sized boards.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Nic. Appreciate the quick response. The problem we're facing is each staff member has anywhere between 10 - 150 records they are working on, and we have approximately 50 staff members. Not all these issues are active, but need to be retrieved for later use. Is there a way to archive issues not active, but available for retrieval or reporting? That way, we only have to import the 'active' issues....
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The most simple way to do this would be to have a "not active" status in the workflow, which you drop from the active boards.
Then have another board (or probably more usefully, just a saved filter) that fetches all the inactive ones and allows you to move them to an active status. You could do something similar with a custom field or label - actively deselect issues from the boards when they're labelled as inactive (or only select ones flagged as active)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Can you have a status not in the workflow status? for example for those inactive issues call them 'Inactive' and in the workflow we have 'to do', 'in progress' and 'done'. Can you do that? And the 'inactive' issues don't get populated on the board? And this would be for jira core cloud...
thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
No, because a status can only exist as part of a workflow. If you had one hanging "outside", you'd have no way to get the issues into the main flow. But you don't need anything like this. A workflow that's inactive -> to do -> in progress -> done is fine. You just tell your boards to only look at the three active status.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
okay, that makes sense. How do you tell the board to only show to-do -> in progress -> done? And not inactive?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Go to Board -> Configure Board -> Columns where the columns are defined.
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.
Ah, you said Kanban board, which only exist in Software. The Core boards are not Kanban, and are not configurable.
The only way I can think of doing this is to have an "active" project and an "inactive" one. When an issue becomes active, you'll have to move it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yeah, I said Kanban board because we are thinking about moving up to Jira software from jira core. It seems to have more functionality (e.g. color cards, quick filters, viewable issues ~3K, etc..) Do you know if we test it out, then decide not to purchase it, will it break anything in our jira core cloud instance?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Show up and give back by attending an Atlassian Community Event: we’ll donate $10 for every event attendee in March!
Join an Atlassian Community Event!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.