Any known work-around for request-type permission limits?

[Jared G]

I recently began using Request Type permissions to limit the view of certain request types for customers.  I was saddened to see that I can only permit up to 50 organizations for any given request type, and we have hundreds of customer organizations.  So far, my only solution that I can think of is to create duplicates of the same request type, and do organization 1-50 on the first request type, than 51-101, etc... on the next, and keep creating more duplicates which is messy and a major pain.

Looking for a work-around.  I researched grouping organizations (you cant).  I also looked into if issue security might work, doesn't look like you can set a permission based on that either.

Does anyone know how I can use just one request type, but have it permissible for more than 50 customer organizations? 

[Tomislav Tobijas _Koios_]

Hi @Jared G ,

When it comes to native solutions, my best guess is using different portals for different groups of organizations. I've tried searching for feature suggestions on expanding the limit that comes with the req. type restriction limit, but I couldn't find any. 
However, you might take another look at the suggestions dashboard: project=JSDCLOUD AND type=Suggestion AND statusCategory!=Done and text ~ "request type restriction" ORDER BY updated 

Additionally, you might want to leave a comment/ask a question on the following post about this as well: 🎉 Announcing request type restrictions in Jira Service Management, or you can also reach out to Atlassian Support regarding this question/suggestion and maybe they can raise a suggestion ticket on raising the limit.

Cheers,
Tom