I believe the limit, while arbitrary, is sensible... The tabs are all pre-rendered so the page generation time could get quite long if there are too many tabs each with expensive queries. After a certain point the maximum runtime would be exceeded and the panel would become unusable.

@mmodell's argument is sensible. Since users can create as many panels as they wish and link them from text panels (without causing any pre-rendering), I think the basic need is covered anyway.

I propose to decline this task. It looks like a clear Wontfix if we report it upstream, based on the same argument explain by @mmodell.

In T76532#806547, @mmodell wrote:

I believe the limit, while arbitrary, is sensible... The tabs are all pre-rendered so the page generation time could get quite long if there are too many tabs each with expensive queries. After a certain point the maximum runtime would be exceeded and the panel would become unusable.

But that's a function of the queries, not the number of panels. I bet I could make a 2 tab panel that can't load ;)

My use case is W494, which is the panel I have of each member of RelEng and their open/assigned tasks.

I won't push on it though, because I guess I'll just use a search grouped by assignee or something. This was just nicer looking.

cc @Aklapper