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.

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!


Detailed Root Cause - Best Practices for detailed logging and reporting in Service Management Cloud



We have used Jira Cloud for a full busy season now, and we are well aware of its shortcomings. We are trying to decide if we want to jump ship or continue the customization process to make it work.

We use Jira in other parts of our business and making the switch would be painful, but doable.

Our company is a startup that sells a handful of highly technical commodities. These commodities (think equipment to get a job done) go through a number of different interactions with customers. The main ones are:

  • Training on their use 
  • Questions in the field
  • Break/Fix
  • Returns/Repairs/Maintenance
  • Parts Orders for self help
  • Rental/loaner (not yet implemented, but were getting there)

Primary Issue: Service Management - Root Cause Reporting

Most of what Jira offers as far as customer support goes has met our needs, albeit minimally. (KB, ticket tracking, portal, issuance, workflow)

The key issue we face is related to our very active customer support team, which is required to deliver highly detailed root cause analysis and reports to the product development team. However, Jira doesn't seem to be setup for this kind of work, at least by default. 

The granularity we are able to collect through Jira is simply not good enough. The best I could find is the tagging solution, which would require us to build a framework of tags.

Has anyone else needed this kind of granularity within Jira and implemented successfully?




1 comment

Hi,  It doesn't look like you got an answer, I'm curious about what you ended up doing?


Log in or Sign up to comment
AUG Leaders

Atlassian Community Events