We have Service Desk set up in Jira Server. Customers have jira accounts and accounts are associated with organizations accordingly under Service Desk customers.
These users create service desk requests through servicedesk portal. Later, all submited issues are visible from servicedesk > company > requests list. Most of the requests when opened work as they should: organization users can view and comment on these issues.
However, very randomly, some issues when opened are displayed with empty box with "No requests found, raise another request."
Issues are created, worked on, transitioned identically, nevertheless some issues are not visible to customers and I cannot figure out why this is happening.
Is the request type filled out on the issue type? As you know you can have multiple request types associated to an issue type. I have noticed before that if the issue does not have an request type present then this can result in some strange errors.
Check this on the associated issue type for the request. There is a field called "request type" visible from inside JSD.
Hi @Per Löfgren !
I think what you are partially referencing is this solution https://confluence.atlassian.com/jirakb/requests-not-visible-in-the-jira-service-desk-customer-portal-777026993.html
I also made sure that all issues have a valid issue type from the projects Issue Type Scheme, although I have a default issue type set up to prevent this. Also, every issue has correct request type with them. I double checked just in case whether issues are maybe relevant to those causes that are linked in the url I provided but everything checks out.
Just in case, I tried manually re-setting valid request type available for current Customer Portal but issue is still not showing.
I have searched in Jira Server database fields if there are some significant differences between issues that are showing and which are not but did not find anything there too.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sorry, that the solution wasn't as simple as that. I believe you need to create a support ticket with Atlassian if you have not done so already.
PS, If they help you find the answer then please post it here. Will be interesting reading
Cheers
Per
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.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.