You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi community,
I'm working on a project which aims to improve the existing service project in Cloud. The project is not in its best shape. For instance, the customers often use wrong request types for their requests since the current set-up is not self-explanatory enough.
To start with, I need to have an overview of the current requests so that I can analyze which requests are most misused, which requests are not used at all, etc. For this, I will use "Reports" and I have to create some custom reports since the default ones are not adequate for my analysis.
My question is more about brainstorming and learning new approaches from experts like you: Which kind of metrics would you use to have the best outcome for my analysis? In other words, how would you start analyzing the current status if it was your project?
Hi @Özge Kavas ,
1. I would run a JQL and see how many tickets were created in each month and for each category. OR use a "Service project report" gadget.
Example JQL: "Request Type" = "Fix an account problem (ITSM)" and createdDate >= startOfMonth()
2. I would also Group the request types in customer portal so that it is more easy for users to find the required types
Thank you very much for your insights! I think it's really a good idea to create a dashboard and examine the requests by type for each month.
For grouping the request types, it's practical to do it if there are many request types. In my case, there are not more than 5, so grouping would mean extra non-value-adding clicks for the end user. But, I agree that it's a good practice for bigger cases. :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.