Why can't I have more than 50 queues in my project?

[Richard Scholtes]

The number 50 strikes me as somewhat estimated to be sufficient.

Is this a technical barrier on Atlassian side or are there "just organisational" thoughts behind it?

[Chad Jackson]

Doesn't really answer your questions, although we were informed by our 3rd party contractors helping build out our JSM environment that it's a hard limit and is not modifiable.

[Nic Brough -Adaptavist-]

@Chad Jackson has the right technical answer, please mark their answer as correct (even if the three of us can agree that we don't like it much)

It is a technical barrier, and Atlassian chose 50 as a limit broadly based on how people generally build queues, how useful many queues might be, and performance.  

The main two points are:

• The human side.  50 queues?  Why are you doing everything in one place with no qualification of the actual problem?  Is it the right thing to do to place HR, office issues, Tech support and Customer queries all in the same project?  Why do you think you need 50 queues for one field of work?  (Don't get me wrong, 8-16 is easy to justify, but over 40 is a struggle to understand)
• The technical side:  Most of Jira works off queries.  Every board, project view, query, report and of course, queue works from a query.  The more queries you have to run to generate something, the slower it is going to be.  As every queue is a query, and could have other filters, running 50 could easily become a problem.