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

JSM to Jira Software integration

We have been running JSD/JSM for about 3 years now, and have minimally integrated JSD to Jira software.  We are in the process of migrating from JSD (Server) to JSM /Jira software cloud.

I am curious if anyone is at a similar stage of JSM usage, and has some tips to share about recommended ways to create a beginner level best practice process for taking a support ticket through the process of escalating it to a change request for the relevant system?   

1 comment

IMO, keep JSM external customer-facing “tickets” separate from Jira internal “issues”.  They can point to each other (say via a directional Link).

Lock down the Jira side to internal folks only, unless your org truly wants to become very transparent to the market (like Atlassian itself).

You can manage the lifecycles of external tickets and internal issues separately, but also keep internal and external communications explicitly separate.


Log in or Sign up to comment
AUG Leaders

Atlassian Community Events