End users cannot add comments to RITM in Service Portal
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-28-2016 07:08 AM
End users cannot add additional comments to RITM in the Service Portal like they can to an Incident ticket. Anyone know how to fix this? I confirmed this is working from end users via the Self Service view through the Service Catalog. I also confirmed that there is a ACL for additional comments on the requested_item table. This didn't resolve the issue.
Thanks for the help!
- 16,859 Views
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-11-2021 02:26 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-07-2017 05:07 AM
Hi All,
I have the same problem.
If the user have itil role, he can comment the RITM by Service Portal otherwise no...
the problem is present only in the Service Portal, if I use the normal ServiceNow page is working correctly ...
Someone have a solution ?
Best Regards
Vincenzo
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-06-2017 01:03 AM
First, i would like to understand, how you are adding the comments on normal ritm self service view for ess user
second, if ACL is restricting the field then end user should not have access to the field in all areas
for the above problem, what we could do is overrid the ACL on task table on the RITM, and give access to everyone, it would work then.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-06-2017 01:14 AM
adding ACL for task.comments for me does not make comments area with "Send" button visible in portal for requests as you can see on screenshot in first post.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-06-2017 02:19 AM
on task.comments it should not have any roles specified in the ACL as updated by vincenzo.basile@live.it it should work i tried it on my dev instance