I've recently made the move to Project 2013 Standard (15.0.4727.1001) and seem to be having problems using even simple filters I've created within custom reports. For example, I wanted to create a simple "show all tasks which are past their finish date" report. Starting simple, I created a filter with one criterion:

"<%Complete> <is not equal to> <100%>"

The report returns only a handful of tasks (mostly summary tasks, if that's any clue) - but many fewer than meet this criterion. This occurs regardless of the Outline Level I select.

This seems so straight-forward I must be missing something - or is this functionality just that weak?

Update: It appears that some of the predefined filters aren't being respected, either. For example, my report only shows one task with the "In Progress" filter applied and only a handful when the "Incomplete Tasks" filter is applied - both clearly wrong.

  • What report are you attempting to run and filter?
    – JulieS
    Jul 16, 2015 at 14:07
  • I'm creating my own custom report with a single table - it's so simple, I'm beginning to wonder whether there is a bug in play.
    – JimMSDN
    Jul 16, 2015 at 14:25
  • That said, it appears that some of the "standard" reports seem to be acting strangely as well with filters applied. For example, on the standard "project overview" dashboard the "past due" table doesn't display any tasks (and there are certainly overdue tasks) - but when I change the filter to from "Past Due" to "All Tasks" I get the listing I would expect. Hmmm...
    – JimMSDN
    Jul 16, 2015 at 14:29
  • The Late Tasks filter uses the Status field, which relies upon the Status date. Is your status date set? Check Project Information.
    – JulieS
    Jul 16, 2015 at 14:55
  • As far as tracking down the issue - apply the filter in a Gantt chart view - does it work as expected?
    – JulieS
    Jul 16, 2015 at 14:56

1 Answer 1


After some continued experimentation, I determined that the degree to which tasks are rolled-up in the Gantt Chart view determines which tasks are "visible" within reports. To solve my problem, I simply expanded all of the subtasks in the plan and the reports then populated correctly. While this seems like a strange way for Microsoft to have designed reporting, this is apparently the PAD behavior. I've searched for a reference stating such but cannot find one - if anyone does, please post it as a comment.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.