Task Based Reports - Parent Folder vs Parent Project Grouping
When I run a task based report, and select Parent Folder as my grouping currently it isn't showing me the parent folder, it shows me a parent project. I understand what it is really showing me in the next org structure, where a task resides. I would like the ability to move 1 step up in the organizational structure, when pulling a task report, not just Parent Project, which is currently a misnomer titled Parent Folder. I would like to see both a Parent Project (properly named) and Parent Folder as options for grouping for task based reports.
I agree, I have a similar challenge. I have a structure as : Customer Projects(Folder)/%Company%(Folder)/%Project%(Project)/%task%. To be able to extract all timelogs and figure out to which client it relates to, its a hard job. This work would be so much easy if the entire Parent Folder tree were displayed in the report.
I think I agree, however... what may work better is to have the ability to mark folders as a "report level." The reason I say this is because everyone's structure is a little different. While doing a 1-up, 2-up, 3-up grouping or filter would work in a lot of cases. There would be some where things would still show oddly.
For example:
2018
>Main client
>>Section client
>>>Team client
....Project
>>>>team 1
------task 1
------task 2
>>>>team 2
------task 1
------task 2
>Main client
....Project
------task 1
------task 2
>Main client
>>Section client
>>>Team client
....Project
------task 1
------task 2
So if I was doing a report on tasks... and I wanted to see the parent folder 1-up, I would get 3 different results
1. Project level
2. Team client
3. Main client
So if we had a way of tagging a folder for reporting. So maybe I know I have up to 5 levels of reporting. So I could designate the main client as report level 2, and the sectional client as 3, and the team client as 4, and the the team as 5... So if I wanted the report to show my Main Client level, I just tell it level 2, if I want to see the team client level then I would pick level 4. If those levels are missing, then it would be awesome to be able to build in logic so where we could tell the system if it's missing to use the next level up or down from the level chosen, but not to go lower than 1 level above the task. So if we pick to report on level 3 say... but it's missing on some projects because of the way the structure is built, I may choose to report those items as is, or maybe 1 level up, or 1 level down.
I'm in favor of what you are asking, just wondering if it could be more powerful.
Hey 👋
I have an update on this request. It's Structured (or Hierarchy) Reports. Now, in Reports, you can see subtasks under their parent tasks and parent tasks under the Folders or Projects.
You can read more about this, and provide your feedback here 👍
Thanks for offering use-cases, votes and examples here!
We need to be able to see the Parent Folder and all folder levels really, in reports. Right now we only see task title, project/folder not parent folder
Hi Charlie Hanks! You can use grouping by folder or projects and the structured reports for this:
You can see that tasks are grouped under subprojects, projects, and folders here. More detail on how this works here: https://help.wrike.com/hc/en-us/community/posts/360001440314-Your-Feedback-Structured-Task-Reports-Hierarchical- Hope this helps!
Lisa Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover
Lisa Wrike Team member Become a Wrike expert with Wrike Discover