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.
Hello everyone! I have a few problem issue types created, however, they don't show on the 'problems' section on Jira Service Project. See below:
Hello @Mariano Gedisman
When you create a custom queue you have to define a filter for it. Please show us the filter for this queue.
Hello @Trudy Claspill ! Thanks for your reply. Can you explain a bit more about your statement?
I did not create anything though; the "open problems" queue was there since project creation, seems to be a out of the box feature from Jira.
I was actually under the impression that Jira would understand this queue should show problem type tickets.
I kind of remember creating a Service Desk project, and jira asking me to relate an issue type with these "special" queues.
When you go to edit the queue for the "open problems" section, you see it like this:
My question being, What is this section for? What's the difference with me creating an Open problems queue myself?
I feel like I'm missing something, and I hope it's not a cool feature!
Thanks again for your interest in helping me.!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, you are correct. I had not worked with that project template before, and did not know about Ticket Categories.
I set up a test project and created issues in it of the Issue Type that is be default part of the "Problems" category, and the issues did show up in my Queue. I was not able to recreate the scenario you see where the issues are not in the queue.
Did you create additional issue types in this project?
Were the issues created through the customer portal? If not, through what process were they created?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi again @Trudy Claspill thanks for replying!
Would really love to learn how to fix this without having to undo the whole project itself. If this happens on production I would guess it'd be a massive headache 🤕
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sorry for the delay in responding.
My suspicion is the system is not finding a "Ticket Category" value for the issues, but I have not seen that as an available field to display on the screen nor to add to the output columns in List View of the Issue Search screen.
I'm stumped. I recommend you contact Atlassian Support and open a support case.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey @Trudy Claspill ! No need to apologise. I’m actually quite grateful you took the time to reply :-)
What’s the best link to open a ticket with Atlassian support? When I Google it, I always end up in different places.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I pull down Products from the top of this page and click on Technical Support.
At the bottom of the Atlassian Support page is a Contact Support button.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
As I recommended to the original poster, I recommend you have your Jira Administrators open a support case with Atlassian Support to investigate the issue.
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.