Incident Tasks missing

[derek_h]

Hi,   we would like to start using Incident Tasks for assigning tasks to different groups so we can keep tasks all together in a single incident.   We noticed that we were missing this tab in our incident view so we have been working with support to get it working.   Their solution still isn't correct but before I go back to them, I thought I'd ask some questions here as well.

We want to have exactly these options available to us, same view:

ServiceNow Incident: Create an Incident Task | IT@UMN

We've tried adding the appropriate related lists to our incident view but we are not getting the Related incident Tasks options.   I've tried in both our Dev and Prod environments.

If we add tasks-release to related lists, we only get a task tab and when we click on new, it has a giant list of options to choose from like Catalog Task, Change Request, etc...   Nothing applicable to what we want.   Ticket-release is also not what we are looking for.

This isn't an optional module is it?   Any ideas of what I might be missing?   Maybe something was disabled when we initially deployed Servicenow that I don't know about?

Thanks for any help,   We are using Eureka.

Derek.

[will_smith]

Hi Derek, you should able to personalize the related lists on your incident table and add Incident Task -> Incident. This should give you the tasks you are looking for.

[derek_h]

Hi William,   Incident Task-> Incident isn't visible as an option for me in either Prod or Dev

[will_smith]

Hey Derek, do you have a ServiceNow admin, or are you the administrator?

It is showing up for me in both my demo environment as well as my client's development environment. Navigate out to an incident form, right-click and choose Related List. In the next window you're not seeing the below image?

By default the Incident table extends Task. Have you made any major changes to the Incident or Task tables?

[derek_h]

I am a servicenow administrator and should have access to everything.

I personally haven't made any changes.   I wasn't the one that deployed Servicenow so maybe something was changed when that was done which was a year or two ago.