Il semble que la page que vous recherchez n'existe pas dans votre langue. Mais nous proposons d'autres contenus en français ainsi qu'une assistance en français.
En quoi pouvons-nous vous aider ?
Learn. Share. Discuss.
Hi,
Currently, there's no option to exclude subtasks for reports, which makes our reports too long since we usually use subtasks. But those subtasks are for internal organization, and should be excluded from the reports...
Thanks,
Pablo
Folllowing List for Post: Crate a report on tasks, but NOT subtasks
[this list is visible for admins and agents only]
Great request
I totally agree with Pablo, we need to have the possibility to exclude subtasks from reports.
It is a big problem for me and my colleagues to keep "the big picture" when the subtasks is part of our reports.
Regards
Henrik Poulsen
@Thread Hi everyone 👋 If you could add your votes to Boaz's request that would be great! Our Product team gets data on all threads, but consolidated votes helps us get more momentum behind an idea.
1,000 times, yes please! We have have our spaces & folders organized in a way to match our team structure & file system. We primarily use tasks for our many small jobs that would be impossible to use a Wrike "project" for, and the individual assignments related to that job are subtasks. I only want to report on when the task is done, not the subtasks. We have a workaround that isn't great & involves using a fake user which means I have to log into Wrike from 2 different browsers to do my creative work or to switch over to managing my team.
YES!! Same issue! Allow suppression of sub-tasks and/or a way to report on sub-tasks would be an additional bonus. Although I did create a custom field to group by to tighten up my report results.
Definitely needed.
It is a request of +3 years ago, any plan to have it?
Thanks.
Alfredo
Hello Alfredo Folla, thank you for posting.
We have a similar thread here, with a "Backburner" status. Our Product team is interested in the idea and it will be reviewed during future internal discussions.
For now, the team is focused on other priorities, so there is no scope to research this at the moment, unfortunately. As outlined in this Community post, the Product team looks at a wide range of data, user feedback, and Community suggestions/votes to determine what next to work on. The team always aims to focus on implementing the functionality that will have the widest impact and benefit for the most users, and it's for this reason, that we simply can't implement all of the suggestions we receive via our various feedback channels.
If there are any changes to this, we'll be sure to update the thread. Please let me know if you have any questions.