Incident Name Appearing as "s" Instead of "Incidents" in List View

Puneet Hegde1
Tera Guru

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!

7 REPLIES 7

Dr Atul G- LNG
Tera Patron
Tera Patron

Hi @Puneet Hegde1 

 

Seems the module name is reworded and causing issues.

*************************************************************************************************************
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]

****************************************************************************************************************

Swapna Abburi
Mega Sage
Mega Sage

Hi @Puneet Hegde1 

please check Module title.

system definition -> Modules and search for Title with “S” and update title as Incidents

Ankur Bawiskar
Tera Patron
Tera Patron

@Puneet Hegde1 

somebody cleared the table label from sys_db_object for incident table and hence it's showing only s

please correct it.

If my response helped please mark it correct and close the thread so that it benefits future readers.

Regards,
Ankur
Certified Technical Architect  ||  9x ServiceNow MVP  ||  ServiceNow Community Leader

Db object does exist in our system, I have checked it and checked all the sys_dictionary table also to identify that someone changed a display name or anything, but did not find anything. We have cloned our instance to the dev, but the name of the dev instance is correct.