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

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
4,466,881
Community Members
 
Community Events
176
Community Groups

Submit your Jira Service Management use case and win!

Hi everyone - in case you haven’t heard, we’re hosting the show of the century on November 10th: High Velocity: ITSM World Tour.

 

ace1463b-cd27-49d0-8fa6-5eccce09423d.png

 

This virtual, concert-themed experience will be filled with rock playlists, photo booths, backstage Q&A, and of course a talented host! We’ll share our vision for ITSM, interview enterprise customers in an “unplugged” session, and dive deeper into a demo of key features in Jira Service Management.

 

How can you be part of the show?

We’re inviting customers to submit their unique Jira Service Management use cases. How is your business using Jira Service Management? What do your workflows and service desks look like? How’s it helping your teams improve service delivery? The answer to those questions could be worth a big donation to charity in your name!

From now through October 14th, we’re taking submissions for the best, most unique use cases for a contest taking place during the ITSM World Tour. The audience will get to vote on the finalists to crown a winner and send a $5,000 donation to charity!

 

How to submit

Complete your submission here by October 14th to be entered to win (only fitting we’re using Jira Service Management for this, right?)

Our judges will deliberate and select a group of finalists who will be notified of their selection via email by October 22nd. The finalist use cases will be presented during the World Tour event, where audience members will vote on the winner! The winning submission will have the opportunity to send a $5,000 donation to an eligible charity from a list provided by Atlassian. Winners will be notified via email and promoted on Atlassian community and social following the event.

Don’t miss out on this opportunity to brag about your service delivery practices and donate to a good cause! Drop any questions in the comment section below.

 

Submit my use case

 

1 comment

I am not sure these are all that unique but this is how JSM is used at my company:

  • It's become the place you to to ask for anything of the company. There are portals not only for technical functions but also Legal task submissions, Human Resources/benefits, Purchasing, Workplace needs, Payroll requests, and Accounts payable requests. More services are being actively rolled in
  • Many of the portals are triage/routing projects. This provides a single point of contact for <insert general thing here> that, between automation and human triage, routes to the destination(s) necessary. This has also greatly reduced the number of times a request simply is created in the wrong place only to need moving at best or not being handled at worst.
  • They tend to be where complexity is housed. Rather than scatter validation, conditioning, and post-function complexity around the entire environment, much of it is all in one place. The maintenance and development of it needs to occur BUT it allows for more sharing. For example, if a given validation is needed across several cross functional teams, if submitted in a single place before propagation, it only needs to be developed, tested, and implemented in ONE place.
  • Keeping all the requests in one place, with more added all the time, means that managers on up need only go one place for the majority of their review/approval tasks all found at one consistent URL. This has proven very popular.
Like # people like this

Comment

Log in or Sign up to comment
TAGS

Atlassian Community Events