How can I create a report that includes the project AND task is one?
Hi,
As a project manager I am task with monitoring who has the bandwidth to take on more projects. The current structure of the tool allows me to create reports by project or by task. This system doesn't a full picture of anyone's work for a given week.
For example the project report can tell me that an analyst on my team has 30 hours of work for the week which tells me they have room to take on about another 10-15 hours of work. The task report shows that same member with 20 hours of work as an assignee and not a project owner. So technically this analyst has 50 hours of work in a 40 hour work week which means she is over 10 hours but unless I look at both reports I wont know that.
Is there a way to capture project owners and assignee's to a task in the same report?
Hi Darcy, thanks for sharing your thoughts about the Reports feature! You are right, it's possible to create a Report that includes tasks or Projects but not both item types at the same time. While I understand that it requires manual effort, I still want to offer you a workaround that might work in your situation: create a dummy task for every Project owned by the analyst so that the start and due dates of a task and a Project are the same. When you run the task Report, these tasks will play the role of Projects and this way the Projects durations will be included in the Report.
Do you think you could tell us more about your use case and how you and your team use Reports, Tasks and Projects? Usually, a Project duration is basically the duration of all tasks included in the Project so there’s no need to take both Projects and tasks durations into account to calculate someone’s workload, that is why I find your case particularly interesting. Looking forward to hearing from you!
Anna G Community Team at Wrike Wrike Product Manager Learn about Wrike’s killer features and best practices with our Online Training Webinars
Anna G Wrike Team member Learn about Wrike’s killer features and best practices with our Online Training Webinars
My team also has an ongoing need for a combined report that shows both tasks and projects. It's very cumbersome to have to switch between two reports to see the big picture for any given project.
Any thoughts on adding this feature?
thanks,
Stacey
Stacey Gill Munich Re
HI
I would also appreciate a reporting view that presents the project name and task information. Is this on your development roadmap by any chance?
Thanks
Judy
Hi Judith, welcome to the Community 😊
it would be great to get a little more detail on what exactly you're looking to Report.
For example, you could use a Task report and use the relatively new feature of Structured Hierarchy feature - let me know if this helps 👍
Would love to see this as a feature as well. Currently, you would have to run two separate reports if you want to see project level data (custom fields) and then another report to see the task data for that same project.
One workaround I found was to view it in the New Table view and then export it to excel, then convert to PDF. It is too much of a workaround so hoping a way to report this way can be introduced.
@Jennifer Hey, thank for bringing this up here 🙂 I'd suggest creating a separate Product Feedback request for this, if that's possible.
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
I agree, this would be very very usefull.
@Jennifer, I've changed this post to Product Feedback post so there's no need to do that now 👍
@All please ensure you have voted on the first post in this thread to add to the voting process.
Would like this feature as well. I'm confused as to why sorting by Parent folder treats Parent projects as a folder. The Structured hierarchy does help with adding the projects under the correct folders, but we can't sort by status like the Custom grouped view.
Hello, I'm new to Wrike as we are 2 months into using this wonderful tool. However, I as well have discovered a gap in report capability between a joint project/task reporting. We have "collaborators" who are struggling to see their work as it relates to the many projects they have initiated. A task list is great for viewing and managing all task but for the high-level perspectives, it's difficult to see tasks as it relates to their many projects.
What I'm hearing from collaborators and users alike — is they would like a report (and maybe dashboard) that shows their projects and project-level information in addition with task level info. it provides a different experience in how they view and manage their work. it's a more natural experience for the end-user and the most requested feature from our team.
Wrike team! is there any new work about this. In my opinion, this is the biggest gap we have run into with the tool.
I would also like the ability to create reports that include both project and task detail. We have collaborators that request 'projects', and then tasks are created as the steps necessary to complete that project. Without a lot of manual effort, there currently isn't a way to send a report to collaborators that includes the project information (including custom fields), and task detail so they can see what steps have been completed, what tasks are upcoming, who is working on each, and the anticipated timelines.
I would like to see this feature as well in the report, the ability to pull from both projects and tasks because our use case is we want to be able to pull a report on the assignee on the task level but be able to see the custom fields on the project level. The assignee is not assigned as the owner.
Hi everyone, apologies for the delay in response here.
The Product team currently have no plans to implement this suggestion into the product. If anything changes here, I'll be sure to let you know.
We would really benefit from this.
Here is our example:
In this quarter's folder we have 590 projects. Toward the end of the quarter, our writing team, artists, researchers, editors, etc. want to know what projects to prioritize for our quarterly cutoff and where each of those projects are in the workflow. Not all projects have the same number of days or tasks, so we can't make a general rule using progress as a way to determine what will "make it". Some projects have 20 tasks, some have 7, etc. depending on the type of work (research, writing, video, etc.)
We have status meetings where we make notes (a custom field) at the project level, but Wrike doesn't have the ability for tasks to "inherit" project level data, so there's no way to ensure that tasks have these notes without manually pulling dragging that information down (which we would never teach our entire team to do, it would be way too manual, tedious, etc. and totally inefficient).
This is problematic when team members want to know about the projects that need to make cutoff and how many tasks they still need to complete in that project:
We can either see Projects by adding their user data to the project level (Example: Writer, Editor, Artist, etc. custom fields), but, then we can't see any of the tasks (we can't see how many tasks are left in a project for that individual). Or we can limit tasks by assignee, but can't see any of the project level custom fields (we can see the tasks, but notes and other relevant data is lost.)
Possible solutions:
I agree, this would be beneficial. One report instead of several.
Hey Lindsey Walters and Kim Oliver, thank you for sharing your use cases and feedback! These have been passed on to the Product team.
I just read through comments from 2017. How has this not been addressed yet? A report that shows information for both the high-level projects and the tasks that lie underneath it seems like a no-brainer? I can't create the transparency needed for my leadership without this functionality- therefore impacting our ability to use Wrike moving forward. Becoming very disillusioned with the system and the time it takes to address what appear to be fairly obvious "improvements"
Hi Lauren Donovan, welcome to the Community!
Currently, the team doesn't have this in their short-term plans. This Product Feedback forum works on the voting system, so we pass the feedback on to the Product team, but once the suggestion reaches the 60 upvotes' mark, the team adds a status to the suggestion. The number of votes helps the team understand the popularity of suggestions here. Here's a more detailed post on what happens with product feedback.
If you're having difficulties, please reach out to your Account Manager or to our Support team, or just let me know and I'll be happy to set up a call for you or raise a ticket 👍
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
I would love to have this feature as well. When we began with Wrike, my team started by creating tasks for certain programs and projects for others. Now, it's hard to double up on task and project (as some programs make more sense to have tasks than others). We want to be able to keep up just so we can pull the report that we need but that seems easier said than done. I've tried multiple different ways to show both but it looks like I can only see reports on just tasks or just projects. As each program manager on my team uses Wrike differently, we need a method that allows us to be able to report on both together. We pull based on custom fields and it would be nice if we could pull both projects and tasks.
Thank you for sharing your use-case here Mary Hess! 🙌
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
I agree with needing a report that shows the project level details including custom fields, along with tasks and/or milestones of a project. This would allow me to track movement towards milestone and provide reports to management on key dates on a weekly project status report.
Welcome to the Community Wendy Richardson! 🤗
Thank you for supporting this suggestion here! Can you please also upvote (= "like") the original post by Darcy at the top of this page if you haven't already? This helps our team understand how popular any given suggestion is. Here's more detail on the process 👍
Please let me know if I can help you with anything else!
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
Lisa Thank you for mentioning the upvoting as I am sure this helps you and the Wrike team! Something I want to mention is that it is very difficult to tell if I have liked something or not as the colors look to be about the same. Definitely recommend that on a Community post, where upvotes are needed, this is adjusted as I would like to make sure I am upvoting content and not removing my vote on accident. Just a food for thought here for those, like me, who thought they had upvoted but cannot tell 😁.
Thank you for mentioning this Mary Hess 🤗
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
I'd like to add my vote to this as well. We have user groups (for example business analysts) that work on specific standard tasks on projects (say, process mapping). What the BA manager needs to see is what work is assigned to their team and what projects those tasks correspond to. Right now this involved a lot of manual work and has a significant impact on usability/adoption of the tool
Thank you for adding your support and sharing your use case Boris Khramtsov!
As a people manager it would be helpful to have a report by employee with all their tasks or projects underneath. This allows me to quickly determine what is on their plate and how to assist or allocate resources. I've liked the original post by Darcy back in 2017.
I suspect that many people have just accepted work arounds like dummy projects, just making two reports, or even just making everything a project or a task so it all falls under one bucket organization wide. Simple thing but could add a lot of value.