Some states don't appear when querying the task table

[markdesouza]

I have a user that is trying to get a view into all of her tasks (incident, change, it request, etc).  She's trying to view the task list where the assignment is herself.  She is trying to filter out states from incidents by using 'is not one of" awaiting problem, awaiting user info, awaiting evidence or awaiting vendor but in the state field she doesn't see the first three items.  We also see awaiting vendor twice.  Why would those items not be there, or in the case of the awaiting vendor, why would there be two entries?  How can we add them?

[Michael Ritchie]

This is where table inheritance causes problems.  The incident table extends the task table meaning it inherits various functionality including attributes, business rules, etc.  Since each application incident/problem/change all have their own states, they apply specifically for those tables.  Your report is running against the task table so it is only showing the states of the task table.  Hopefully this makes sense.

[Michael Ritchie]

You could set the "glide.ui.list.allow_extended_fields" system property to true which will allow reports and lists to filter on the extended attributes.  This is documented here at the bottom:

https://docs.servicenow.com/bundle/kingston-platform-administration/page/administer/list-administrat...

[Scott Jordheim · Accepted solution]

Something to be aware of as well: If the numbers tied to the various record States are the same when that properly is set to true, weird behaviors will arise when reporting from Task.

IE - If Closed Complete on Request has the same State number as On Hold for Incident, they will fight each other. They may have to design filters around that.

[Kamer Taj]

@Scott Jordheim 

Thank you so much for the explanation.Then what will be the solution for this issue.Even i am having same issue.

Regards,

Kamer Taj