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

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage
Highlighted

JIRA Service Desk opinions Edited

Anyone on here using JIRA service desk for your helpdesk software? If so, what are your opinions of it?

I've been assigned another site, and I'm hitting my limit when it comes to keeping track of shit, so I've requested they seriously consider a ticketing system. Looking at starting with the 3 user license of JIRA service desk to start, and maybe purchasing an actual license after getting used to it. https://192168ll.onl/ https://xender.vip/ https://testmyspeed.onl/

Also, are there benefits to integrating Service Desk with Confluence (and HipChat)?

5 comments

Hi Ryan,

if you haven't been using a ticketing system before, Jira Service Desk (JSD) will be the way to go for you. Integrating Confluence (for documentation & knowledge base stuff) and a real-time collaboration solution (Hipchat is not anymore), make keeping on track even better. You can use Slack (Cloud based) or some (free) alternatives (Mattermost, Rocket.Chat) for this. All integrate easy into JSD.

You should try to differentiate between three channels:

* JSD for customer (or inhouse) ticketing

This is a process based channel (Open -> In Work -> Review -> Done).

* Confluence for documentation & knowledge keeping

Create pages or common answers or check lists to go thru to solve a problem. Confluence takes care of versioning, archiving, history etc.

* Real Time collaboration tools (Slack, Mattermost,..) is for fast real time communication around tickets to get the right people on board in seconds

Messages exchanged here are not needed to be archived. They can, if needed attached to a JSD ticket as a comment or added as a comment to a Confluence page. On the other way around, each created ticket, page etc. can trigger a new message in team space in Slack/Mattermost. You can directly post these messages to defined channels of a team. Even email integration is build in (Sending & receiving, if needed....)

To come back to one of your initial questions:

We used another ticket system before (OTRS: Heavily email based), and switched to JSD two years ago. We never looked back...

Best

JP

Like saamhocks likes this

Download Gb Whats App Latest version 2020 - https://gbapkbyte.com/gb-whatsapp/

Comment

Log in or Sign up to comment
TAGS

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you