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

Setting up Service Desk environment

I have some questions about best practice how to set up our Service Desk environment. We have 8 teams and all of us both handle support and development issues. We have been using Jira for all issues up until now. At this time we want seperate our support issues and handle them in Service desk.

Our plan right now looks like this.

1. All teams have their own Jira project for development issues.
2. All teams have their own Jira service desk project for support issues.
3. If a issue should be moved to a another Service desk project we have a custom field that automation listens for and we make a clone of the issue and delete the original.
4. If a Service desk issue should be moved to Jira we have a custom field that automation listens for and we make a clone and delete the original.

Please give me some input if this is a good practice.

0 comments

Comment

Log in or Sign up to comment
TAGS
AUG Leaders

Atlassian Community Events