Application Access Request IssueType workflow for a Jira Service Desk

[Jason Michaud]

We are planning to build out an Application Access Request issuetype into Jira Service Desk and wanted to gain input from the community on best practice.

Right now we use a totally separate tool and now want to integrate that workflow into a new issuetype into our Service Desk on Jira. We have 30+ applications for them to choose from. The question is should we have the customer submit one Access Request issuetype and then within it - they can select all the applications they need access to and then once its approved - sub-tasks get broken out based on each application chosen.

Or should we require the customer to submit a separate application access request issuetype for each application they need access to?

Thank you for your input!