Users not able to see tickets under 'My Requests' EC
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-26-2025 01:17 AM
When any user navigates to Self-Service > Employee Centre > My Requests, the user should be able to see the tickets which he/she 'OPENED' or is 'CALLER' or 'REQUESTED FOR'. There has been an issue regarding the same. Few users (Opened By/ Caller/ Requested For) are not able to see those tickets under the 'My Requests' section of EC. This seems to occur only for few users, while it is working for rest others. Initially, this was reported for 'Opened By' users, and now 'Caller' users also.
We checked for those users. They are active users ofcourse, they have nothing to do with the group/roles since all system users should be allowed to view their tickets.
We checked for the Request Filter. It includes the opened by/caller/requested for users to be DYNAMIC me.
We checked for the ACLs. They allow the logged in user the ability to read those records.
We're not able to figure out what's causing this.
Is this related to some filter in widget configuration or something else?
Any guidance or help is genuinely appreciated.
Thank you in advance!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-26-2025 11:28 AM
Hi @curr_user,
as you said it works for some while it doesn't for another users... it indicates the query/filter condition to be the culprit. If it was a widget related then it would be either all or none.
You said it cannot be role/ACL related, however try to use impersonation for these users whetehr they can view the records in a list view. If they see it in backend list view and not in Portal, it might be a problem with widget
Eventually compare the OK and notOK users - their role, department, location, preferred language, groups ... any pattern would be helpful to debug.
Also, in backend there is Access analyzer that could give you some idea.
If it is client's instance and no debugging will resolve this, you can ask ServiceNow team to assist you via HI Case:
https://support.servicenow.com/now
Good luck and keep me posted
/* If my response wasn’t a total disaster ↙️ ⭐ drop a Kudos or Accept as Solution ✅ ↘️ Cheers! */
