Is there a way to relate a Service Request to a Problem?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-08-2022 03:30 AM
Pretty much as the title says.
We're creating a number of Service Requests so users can request work arounds to specific problems. Is there away to relate the SR to the Problem?
When I look at a problem I want to see how many requests have been raised for it.
I know I could just report on the SR, knowing that it's been created for this problem but I want to have some sort of relationship between the problem and the SR.
Is that possible? I can't really find a related list for it..
- Labels:
-
Scripting and Coding
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-08-2022 04:06 AM
You can add m2m [Many to Many] relation between Request and Problem and update the related list on Request & Problem table views.
Thanks & Regards,
Vasanth

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-08-2022 04:18 AM
Hi Spike,
You can do this by creating a m2m relationship between these tables .After that create a UI action (i.e Create Problem) on incident form. Under UI action, by using a javascript call the m2m table which created and insert a record.
Mark my answer correct & Helpful, if Applicable.
Thanks,
Sandeep

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-08-2022 04:22 AM
The relationship doesn't exist between problems and Service requests OOB.
That is because the two processes have no relationship. May I ask why you are trying to do this?
If the use case is letting users raise software bugs via self service, you may want to look into using Agile Teams and Defects.
ServiceNow Nerd
ServiceNow Developer MVP 2020-2022
ServiceNow Community MVP 2019-2022
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-08-2022 04:36 AM
A Problem is per definition a way of resolving Incidents. A workaround can be used if it's available to make sure the Incident doesn't bother the users that much (their work can proceed). Your end users are reporting that they can't do something and need the workaround. From the definition point of view these are incidents (known issues, but nevertheless incidents).
Why create service requests for this? You are providing Problem workarounds because something isn't working.
If you really want to go this way, I would go for a 1-to-many relationship (the request will only provide a workaround on 1 problem), but look at your process.
If my answer helped you in any way, please then mark it as helpful.
Mark
Please mark any helpful or correct solutions as such. That helps others find their solutions.
Mark