Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Application Access Request IssueType workflow for a Jira Service Desk

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!



Log in or Sign up to comment