Instead of 1 to 1, allow Groups to have many Plans
Right now, groups have a 1 to 1 relationship (1 Group = 1 Plan), would be nice for a single group to have multiple plans
!! You can now create a new plan within an existing group!!
Once you open the “New Plan” dialog just select the link to add to an existing group. Your new plan will then be added to that group, leveraging the existing group infrastructure.
For more info, checkout the support documentation: https://support.office.com/en-US/article/create-a-plan-in-microsoft-planner-93e65b03-6fac-4661-a502-e3161475ab93
120 commentsComments are closed
Alex Henry commented
The inability to do this is a red-flag for me unfortunately. I'm excited to try out Planner once my employer upgrades to Office 365 but this is a barrier that will make it hard to get coworkers to buy into it.
Sures Ramani commented
If every plan creates a new group , that adds an unnecessary overhead. One group and multiple plans seems a great way forward
That could be the basic for our requirement to have a team view.
A team is group of persons which work in several groups. To see the workload of the team members we need an overview of all task per each member over all related hubs. Also a timeline across different groups would be appreciated.
Kazuteru Sakaida commented
Really Good !
We do this now by creating sub groups -- the only problem with that is the groups are not linked together. I'd love to be able to take a larger task (like an Epic) and break it down into sub-tasks. I'd ALSO like the ability to move one of those sub tasks from one plan to another. For instance, we're using Planner as a Kanban board. I'd like our Support Team to be able to put bugs and feature requests into a separate Plan, and allow us to move them from that to the Backlog bucket in another Plan.
Dimitris Foukas commented
It is essential that we allow multiple Plans for Groups otherwise integration with external systems becomes entirely impractical. As a typical Use Case consider integration with Dynamics CRM: we would like to use Plans for Opportunity lifecycle, Case workflow, Contract negotiation, Order fullfilment, custom Projects etc. In line with existing CRM - doc library integration we need to have a common "context" between the two, for example the Opportunity name would be used in the first case. Otherwise hard limits on Group creation (think currently 100 per user) would make this association impractical!
This also goes together with the notion of Plan templates - perhaps we can mandate a SINGLE template with a Group which acts as a placeholder for multiple Plans. This template will define all the required metadata useful for the integration as well as constraints in transitions between states (buckets), custom status codes (instead of the stock Not Started - In Progress - Completed), AAD permissions required to trigger these transitions etc.
It would be also interesting to be able to link new Plans to existings O365 Groups...
Not having multiple plans per group is kind of a dealbreaker for me using Planner. I want one plan per project, but not one group per project (which adds way too much overhead).
Would also be nice to see a use case of using a plan as a single user as a todo list - I have to create a Group to do this which seems a little heavy
can't you just use a new board for as a new "sub-plan" for that group?
Rajesh Kumar commented
I think this make sense since group are like lite team sites and you might be running more than one project for teams
Lisa Strong commented
And hopefully this would also cut down on the amount of emails generated by Planner!
Don C commented
Yes to this! We have a handful of teams (groups) and each team works on dozens / hundreds of small projects (plans). Having a group for each plan is more of cumbersome for sure, but multiple plans per group sounds awesome!
Kevin Baum commented
I think groups are a strong concept and having a plan as part of a group works well. I do however strongly suggest that a single group should be able to have multiple plans. The default permissions would be the same as the "parent" group however could be modified for the specific project.
Federico Williams commented
Agreed. And further, the ability to assign access/permissions to users for each plan would be fabulous.
Really need this!!!
Great idea, so my marketing group could have a plan for each new proposal going out the door without being a part of 30 different mailing lists. Corporate management could have a plan for various internal initiatives.
Mark Casson commented
I agree with Peter, don't make it mandatory to associate a Plan with a Group. Not sure about 1 Group ==> multiple plans, I think Microsoft need to think this through carefully within concept of Groups.
It would also be nice to be able to create plans without the necessity to create an office 365 group at all.
Chaz Weber commented
This would be extremely useful if you're assigning plans or tasks to an organization