1000 Sub-issues limit

Andreas Mouritsen

Our organisation has recently run into the "1000 sub-issues limit".

After looking for answers or details on this issue, I've been left guessing what it actually means or how I can resolve it.

I am currently managing a JDP board with 250 ideas that link to various different epics.

Only when an idea reaches a certain status (out of 7 statuses) will there be jira issues/epics linked to the delivery.
At the moment we have around 20 ideas with issues linked in delivery.
Once and idea is set to "Done" it is automatically archived.

Though even after archiving 4-5 ideas in the last week as a huge piece of work had finished, we started getting the warning as shown below.

Nothing seems to be broken at first sight, but I cannot find any information regarding the warning and don't know what the limitations are and what they may cause.

Tanguy Crusson

@Andreas Mouritsen @Chris Timms currently the calculation of the progress is done client side. That means that every time you open a project it goes and fetches all delivery tickets and their children to calculate it. Obviously that won't scale. We're moving all this to the backend in the next few weeks, which will make things much faster (and also we can cache results etc.).

In the meantime we've applied a limit so this doesn't impact the performance of the frontend: if you get to 1000 delivery tickets+their children we currently stop there. That means that the progress calculation may be inaccurate in some ideas. It currently doesn't exclude archived ideas.

All of this will be fixed by the work we're scoping out now. In the meantime I would suggest unlinking the delivery tickets for the ideas you don't care about that much (e.g. archived or done or just not that important), and avoiding linking epics with hundreds of tickets (we heard that's a thing!).