Kylie Sabra
My feedback
-
904 votes
Hi everyone,
We have updated our Copy Plan experience – please try it out today!
This improvement includes the ability to choose an existing group or team to copy the plan into (or choose to create a new group). You’ll also be able to customize what gets copied over. Attachments can only be copied over into existing groups/teams.
You can get more details here – https://techcommunity.microsoft.com/t5/planner-blog/expanding-the-copy-plan-and-filtering-features-based-on-your/ba-p/1483491
An error occurred while saving the comment Kylie Sabra supported this idea ·
-
1,226 votes
Dear Planner users, Planner is looking to learn your experience with managing “personal tasks”. The feedback you provide would help the product to optimize the features toward your needs, and would benefit other users who use the product like you.
We’d very much appreciate if you could take 7-10 mins to fill out this survey. Thank you!
Kylie Sabra supported this idea ·
An error occurred while saving the comment Kylie Sabra commented
The fact that Planner is creating a group for every plan is making it virtually unusable for me. I'm a writer and have dozens and dozens of blog, web, marketing projects. Each needs a plan, but because of group sprawl, I can't do that. So now I have to create checklists for each blog post, marketing project... Now I can't assign individual tasks, because those are now checklist items. I can't use labels, because they can't apply to individual checklist items. All of my blog posts have to go under a plan called "Blog Posts". It is almost not worth tracking at all. Pleeeeeeeeeease fix this problem. You should not have to create a new group every time a plan is created.
I was shocked to read that if I updated items in a copied plan it would also update the original. :( It is critical that copying a plan does NOT create a new group. There is currently no option to assign a copied plan to a new group. This results in a LOT of unnecessary work as I use the same plan format over and over again. Please fix soon.