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

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

The customer portal search is not showing all issue types or status types.

We have three request types (feature, bug, support):

Service Desk Landing Page.png

Which logically matches our request type configuration:


Requests.pngHowever on the requests search page does not show all three types (missing suggest improvement):


Request Search Types.png

And even though our workflow has the following states:

Workflow.pngThe service desk search only shows two states (open and closed):



What is worse, the open state shows rejected items also:request search open shows rejected.png

Right now this is a terrible experience for my customer:

1. They can't see feature requests

2. The open list constantly reminds them of all the defects we rejected. 

3. They can't filter by the states of our service requests.

How do I get the service desk to map to the request types and states we have internally (which should really be the default)?


1 answer

0 votes
Tessa Tuteleers Community Leader Oct 04, 2019

Hi Guy, 

I'm going to try and answers your 3 questions: 

1) The "feature requests" are not visible for your users: I'm assuming the logged in user doesn't have any feature requests to look at. The list shows only the "available" options, because the list would be really big otherwise with a lot of types having no issues in bigger environments. Can you confirm that that particular user your are viewing does have open or closed feature requests and they really aren't shown? 

2) the Open and closed are basically filters in JIRA between unresolved and resolved tickets. For Jira, a ticket is closed when it has a resolution. I'm assuming the resolved tickets which are still shown in "Open" are still unresolved. You could and should add validators on transitions closing tickets, that a resolution is required. 

3) The users can indeed not filter by status, but when your closed tickets are gone from there, that hopefully won't be such a problem anymore. 


Hoping this helps, 


Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira Service Desk

The Complete Guide to Atlassian for ITSM

Hi Atlassian Community! This is Teresa from the Atlassian team. My colleague Paul Buffington @Buff and I are excited to share a brand new ITSM resource we’ve created – "The Complete Guide to At...

2,211 views 14 22
Read article

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