Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

×
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

Using JSM for Access Requests

We're using the ITSM Template in Jira Service Management. We're trying to decide if we want to use the Service Desk for Access Requests as well or create a separate project. Our IT Team doesn't handle all access requests or at least we don't approve all access requests. My thought is that if we use a separate Access Request project we can better track the provisioning an deprovisioning of accounts. Or are you using one Service Desk project to do both? If so, how are you handling approvals by people who aren't agents or don't have access to the project? How are you tracking deprovisioning of an account? 

1 answer

1 accepted

1 vote
Answer accepted
Mathew Lederman
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Nov 03, 2023

@Steve Fitzgerald I think the best approach would be to create a new Request Type for the Access Requests and possibly a separate Issue Type to keep the items separate from others. You could also create a unique workflow that would identify the appropriate approvals or use a shared workflow with post-functions. This would keep everything within the same project and portal for your customers, but splits the requests so each team only needs to watch their Issue Type.

Approvers for Service Desk projects do not need to have a Jira license at all, so that's not an issue. 

We have our Active Directory connected to our Service Desk via Insight that pulls in Manager (along with many other fields from AD) and such requests generally go to the user's manager for approval.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events