Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Have we hit a maximum number of tasks?

We are using JIRA free and have suddenly hit an issue where new tasks (at top level, not sub-tasks) are no longer visible in the Kanban card stacks.

We can add new tasks fine, and can search and find them using the searchbar, but they don't appear in the card stacks we have set up to manage the pipeline - making it impossible to manage work as there is no visibility of pipeline and work allocated....

Seems to stop at task 750 (we only have 76 that are open, all others are closed).

Is this a bug or a limit we are not aware of.

An ideas on how we can resolve this in the current project without migrating open items out to a new project?

1 answer

Hi @Richard Perry -- Welcome to the Atlassian Community!

There are data storage limits, and I do not believe there are issue count limits:

What you describe seems to indicate the new tasks do not match the filter/display criteria for your board.  Please compare two issues (one that displays and one which does not) to note the differences and that may uncover the problem.

Kind regards,

@Bill Sheboy - thanks for the answer, I can confirm we have checked and that the filter / display criteria are not affecting visibility. We then checked the data storage limit, this didn't seem like a storage issue but upgraded to the standard subscription from free. This should have resolved any storage issue, but still newly added tasks are not visible.

As we are now on standard plan I have raised a support ticket with JIRA along with account access and see what they come back with.

Thanks for your help

Thanks, Richard.  When you hear back from support please post back here what you learn.  That will help others who encounter this same symptom.  Thanks!

It turns out that we were using Kanban view but one of the team implemented the backlog feature, despite this not normally being used for Kanban.

This meant all new tasks were added into backlog. They could be added to Kanban but access the "backlog" from left slide-out menu ad then dragging each into the Kanban.

But, we opted to turn this backlog feature back off again in admin section for the project.

Response from Atlassian:

"Someone has enabled the 'Backlog feature'. The backlog comes from the Scrum framework, where work is planned in sprints. By default when you enable the backlog all issues go to the backlog by default, this cannot be prevented and is part of the idea of the backlog. Normally in Scrum the backlog would grow and you would select issues and plan sprints, when you have a Kanban project with a backlog you don't have 'Sprints' but when you are ready to work on an issue you move it from the backlog to your board.

For full details please see:

If you don't want the backlog active you can disable it in the project settings by selecting 'Features' in the sidebar and toggling the feature off. This will cause all items on the backlog to be shown on the board."

Like Bill Sheboy likes this

Thanks for the follow-up, Richard. 

I have helped lots of teams who use Kanban with a backlog, particularly when they have a cadenced queue-replenishment meeting with stakeholders to balance capacity and demand.

Suggest an answer

Log in or Sign up to answer
Site Admin

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you