Filter Reports on Tasks by Project.

Hi Brent :) I saw that you started a chat about this as well. It sounds like you have a parent Project with Subfolders. Right now if you run a task-based report and group by parent Folder, then you'll see all the tasks organized into buckets based on the Project/Subfolder they're in. It sounds like you want to see all tasks grouped under the main parent Folder instead of grouped by the Subfolders as well. Do I have that right?

+1 

That filter would be exceptionally helpful - we break our projects out into its different phases by using sub-folders. The reason we broke it out this way is due to the fact that as a project transitions from one phase to another it also transitions between our teams. However, when we report on any one task, you see the sub-folder (child) not the project folder (parent).

I would also like to request this - the suggested workaround of using the Parent Folder is not suitable unless all tasks exist in a single flat folder structure, which ours do not. A 'Parent Project' selection (which goes upwards through the hierarchy ignoring any folders and returns the first Project name it finds) could be a suitable solution.

Alternatively, this could be solved by more options to do with custom fields. For example, we use a Request form to create new Projects, which adds a Prefix to all folders and subfolders. If we could search based on this Prefix, or if that prefix could additionally be written into a custom field which we could then group the report by, we could achieve what is needed.

Hi Liam, thanks for your input here! I just want to clarify one thing: would you like to run a search within a Report for tasks with a specific prefix?

That would be one way to address the issue, yes, providing that projects are created using a request form from a template. Ours will be so this would meet our needs, but there would be use cases this would not solve for other people.

Hey Liam, I definitely agree with that! I appreciate the info about your use case though, it's always great to learn about different sides of the same request.

Yes, I need this too. I think the original concept of using the parent folder as a column worked well if you put all your tasks under the project. But if you subfolder anything under the project, then those tasks lose their connection to the project they are for in the report.

For example:

Project 1:

...task 1

...task 2

Those would show up in the report with the parent folder showing as "Project 1" which is helpful.

However, if you used a structure like:
Project 2:

>Team 1

...task 1
...task 2
>Team 2

...task 3

...task 4

Then those show up disconnected from their project.  So Task 1 will have a parent folder of "Team1"  which doesn't tell me anything.

So having the Project be a column would be super helpful.