Skip to main content
Question

[New SSP] Shared incidents do not appear in the Self-Service Portal search results

  • May 11, 2026
  • 2 replies
  • 10 views

Otavio Augusto Bosa
Forum|alt.badge.img+2

Hi TOPdesk Community,
ย 

I'd like to report an issue we've identified in the New Self-Service Portal (SSP) related to the search functionality for shared incidents.

๐Ÿ” Issue description

When an incident is shared with another user (via the "Shared with" feature on the incident card), the shared incident does correctly appear in the recipient's "My Requests" page (/services/app/ssp/requests).

However, when the same user tries to search for that incident using the SSP search bar โ€” for example, by typing the incident number (e.g., C2508-3322) โ€” the incident does not appear under the "Requests" tab in the search results.

The search returns 0 results under Requests, even though the user has legitimate access to that incident through the share feature, and the same incident is visible in their "My Requests" list.


๐Ÿงญ Steps to reproduce

  1. As Operator A, create or open an existing incident.
  2. Share the incident with End User B using the "Shared with" field on the incident card.
  3. Log in to the New SSP as End User B.
  4. Go to My Requests โ†’ confirm the shared incident is listed there. โœ…
  5. Use the search bar in the SSP and type the incident number (or a keyword from the subject).
  6. Open the Requests tab on the search results page โ†’ the shared incident is NOT listed. โŒ


๐Ÿ“Š Expected behavior

The SSP search should return all incidents the user has access to, including:

  • Incidents where the user is the caller.
  • Incidents where the user is listed under "Shared with".

If a user can see an incident in "My Requests", they should also be able to find it via search. The two views should be consistent in terms of accessible data scope.


โš ๏ธ Current behavior

The search appears to be filtering results based only on the caller field, ignoring the "Shared with" relationship. This creates an inconsistency between "My Requests" and the search index.

ย 

๐Ÿ–ผ๏ธ Screenshots

1. Incident C2508-3322 shared with the user (Operator view โ€” "Shared with" section): (screenshot 1 โ€” incident card showing "Compartilhado com" / "Shared with" list including the user "Ana Claudia Prates Santos")


2. Incident visible in "My Requests" for the user it was shared with: (screenshot 2 โ€” SSP "My Requests" page showing C2508-3322 listed with the "Shared by Pedro Henrique Amigo" indicator)


3. Same incident NOT returned in the SSP search: (screenshot 3 โ€” SSP search results for C2508-3322 showing Requests 0 โ€” no results under the Requests tab, despite 16 total matches in other categories)


ย 

๐Ÿ› ๏ธ Environment

  • Product: TOPdesk SaaS
  • Module: New Self-Service Portal (SSP)
  • URL pattern: /services/app/ssp/requests and /services/app/ssp/search
  • Tested on: Chrome (anonymous/incognito session, to rule out cache).


โ“ Questions for the community / TOPdesk

  1. Has anyone else experienced this behavior in the New SSP?
  2. Is this a known limitation of the new search engine in the SSP, or should it be reported as a bug via support?
  3. Is there any configuration / permission setting that controls whether shared incidents are indexed for the SSP search?
  4. Is there an ETA for aligning the search scope with "My Requests" scope?


Best regards,
Otavio Augustoย โ€” TOPdesk Specialist @ Brazil

2 replies

Sanne van Opstal-Brakel
Community Manager
Forum|alt.badge.img+11

โ€‹@Otavio Augusto Bosaย if you come across issues like this it's always best to report them to support so that they can have a look with you and decide if it's a bug or not and thus notify departments internally. Or if it's something they can help out with themselves.ย 


Otavio Augusto Bosa
Forum|alt.badge.img+2

Hi โ€‹@Sanne van Opstal-Brakelย !

I've already reported this to local support, and they informed me of the following situation:
ย 

"We've identified that the error is a previously identified bug, and our development team is working on a fix.
To date, we haven't had any updates. If there are any updates, you will be notified via email through this same ticket.
We don't have a specific bug tracking link, as the issue is handled internally.
At the moment, there's no workaround other than using "My Requests" to search for/track the ticket."


However, since several days have passed since the issue occurred, I'd like to check if anyone else is experiencing this difficulty.