"Dead" Projects Still Showing Tasks for Users

[KristofferMi1]

We have noticed that when we've changed the status from "Current" to "Dead", any tasks assigned to users still show in their lists.  When you change the status from "Current" to "On Hold",  task are removed from their lists.  I would think the same would happen for "Dead" projects since they are not required any longer.  We are able to add a filter to remove tasks from these projects, but this will still impact resourcing.  Associates assigned tasks for "Dead" projects will have skewed data for resource management.  Are we missing a step when changing the status?  Thank you!

[Lyndsy-Denk]

Hi, @KristofferMi1. Where specifically do you see this inconsistency?

If it's a report that was built for your instance, I would check the filters to make sure they're excluding projects with certain statuses. Also check to make sure you're using the right filter qualifier because you can filter statuses in a couple different ways:

1. The precise status
2. What that status equates to, which will capture any status that falls into the Equate to category (see screenshot for some of my system's statuses)

If these tasks are showing up in the Home area widgets (My Work or My Tasks), I can see two possibilities:

1. The individual hasn't set the right filters.
2. There might be something about your Status configurations in Setup, especially the Equates With classification.

[KristofferMi1]

Thank you for the response, Lyndsy.  Our "Dead" status for projects is set to equate with "Dead".  But when a project is set to "Dead", all the tasks still appear for any user that's assigned a task for that project.  We could just filter those tasks from all their views/reports, but those tasks are still active tasks and assigned to them.  I would think a "Dead" status would remove the tasks much like "Planning" does.