Incident Name Appearing as "s" Instead of "Incidents" in List View
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-05-2025 03:42 AM
I have noticed that in the list view of incidents, the name appears as "s" instead of "Incidents," as shown in the attached screenshot. This issue is affecting visibility and makes it unclear what the column represents.
Has anyone else encountered this issue? If so, is there a configuration or setting that needs to be adjusted to correct this? Any insights or fixes would be greatly appreciated!
Thanks in advance!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-05-2025 04:50 AM
You might be trying to make a change and save it, once. Try clearing the cache and then apply the change again.
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.
Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/atul_grover_lng [ Connect for 1-1 Session]
****************************************************************************************************************
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-05-2025 05:05 AM
Go to incident table in sys_db_object and see what's the label there
Also check if somebody has written script to change the label using DOM manipulation
If my response helped please mark it correct and close the thread so that it benefits future readers.
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-23-2025 01:58 AM
Hi All,
I had contact with servicenow on this, and this is a known issue if the instance is using any other language except the default language. servicenow has fixed the issue in the Yokohama release. and they mentioned that they will provide a solution to the existing tables. i will update the communication once I have my answer and my case is closed.
Thank you,
Puneet