Date range not pulling correctly for report in text mode

In your current setup, you are asking for three filters: Task with Proofreading for a portfolio between Nov 1 and now. Then you have tasks that contain BPS Review, and then tasks that contain Production File.

If you want the data range and portfolio for all the tasks, you have to include them in your filters.

project:portfolioID=5bdb34fa00435dfb1b0179ebac27d6a1

project:portfolioID_Mod=in

task:actualCompletionDate=2020-11-01T00:00:00:000

task:actualCompletionDate_Mod=between

task:actualCompletionDate_Range=$$TODAY

task:name=Proofreading

task:name_Mod=cicontains

OR:1:project:portfolioID=5bdb34fa00435dfb1b0179ebac27d6a1

OR:1:project:portfolioID_Mod=in

OR:1:task:actualCompletionDate=2020-11-01T00:00:00:000

OR:1:task:actualCompletionDate_Mod=between

OR:1:task:actualCompletionDate_Range=$$TODAY

OR:1:task:name=BPS Review

OR:1:task:name_Mod=cicontains

OR:2:project:portfolioID=5bdb34fa00435dfb1b0179ebac27d6a1

OR:2:project:portfolioID_Mod=in

OR:2:task:actualCompletionDate=2020-11-01T00:00:00:000

OR:2:task:actualCompletionDate_Mod=between

OR:2:task:actualCompletionDate_Range=$$TODAY

OR:2:task:name=Production Files

OR:2:task:name_Mod=cicontains

Also, over the years, I have learned I'm not the biggest fan of Contains filters. They take a long time to load and are not always accurate as someone might have Proofing or BPS Rev.

I use with my teams now a "tag" which is just a field on a custom form they can use to tag their tasks and then we use that for reporting. That way if one client likes to call it editorial and one likes to call it proofreading, we can have that be on the tasks, and we can still get unified reporting. After creating the custom field on a task custom form, I just create a view for them called "Tagging View" which has all the fields they are used to but with the extra column so they can easily in-line edit. Just thought I'd share that with you. :)

Anthony