Can a task be identified as non-critical?

[Kevin F.]

I have a task which can extend beyond the project end date, but is not
critical to completing before the end date. Is it possible to identify this
specific task as non-critical so that it doesn't show up on the critical path
filter?

 

[John]

I have a task which can extend beyond the project end date, but is not
critical to completing before the end date. Is it possible to identify this
specific task as non-critical so that it doesn't show up on the critical path
filter?

Kevin,
Sure, go to Project/Filtered for/More Filters and select the "Critical"
filter and then "Edit". In the filter definition window add the criteria
for the Task Name of the extended task to "Does not contain". Or, you
could use a flag field to identify that task (in case you ever want to
change the Task Name) and only show tasks with the flag = "no" as a
second criteria of the "Critical" filter.

Hope this helps.
John
Project MVP

 

[Kevin F.]

Thank you John. This works perfectly!

 

[Steve House [Project MVP]]

How is it possible for any task ever to extend beyond the project end date?
The project end is when all of the work in the project has been completed.
If any work is left to do, the project is not done yet. If a task is in the
project, it represents work that is part of the project. A project is never
considered ended until all of the work on all of the tasks is completed.
Ergo, it is impossible for a task to ever extend beyond the project finish
date since such a delay pushes back the finish date accordingly. It is true
that tasks might take place after a project's required finish deadline but
that's something else entirely - that's a project that is finishing late.
But the project end date and the project's finish deadline date are two
different things.