![]() ![]() The hierarchy then looks like this, with a single top level entity (Platform Company) The top team is not counted it: it is the team that the list is being published from. In this case I have four teams that can be used to receive task lists. Leaf rows with a TeamID are teams that tasks can be published to. In the example I have set up that two teams (Platform Firstline and eTeam 2) are Maintenace teams (they have that property set to 1) and the rest are without a property. My example also doesn’t have too complex hierarchy defined (only one root that spreads out to different leaves). However do not forget the read the Docs about setting publishing up for more details. Yes – I know that those names are not the best example (far from it) but perhaps it however makes it more clear how this hierarchy can be set up. TargetName,ParentName,TeamId,Size,Departments:Maintenance, #Contract, #OnSite So here is the hierarchy file I used – TeamID I replaced with a text. □□ So take that as a learning: do not set them in the hierarchy file. I had strange errors when I tried to set these. In the hierarchy you just leave these values empty for all teams. If that bucket in Planner doesn’t exist it will be created. These are actually definitions for buckets where tasks will be written in Tasks (Planner) in the team. You could add more “checkboxes” for Departments by defining more columns “under” that Department. The difference between these two is that I can specify the values freely for the Size for each team and Department:Maintenance is a 1/0 (or true/false if you prefer) setting for each team. Then you can set properties how you can limit the teams where the list will be published to. ParentName (parent name from the hierarchical structure).TargetName (ie: the name of the element shown in the hierarchical structure).This seemed to be a bit tricky one – I had to do this a few times to get it right. Keep that open as well when configuring the hierarchy. I am not defining every step on preparing the tenant for Task Publishing (chapters 1-2) in full detail since that documentation found here is very detailed. If you are looking a guide how to create and use Task Publishing then skip directly to chapter 3 (creation of lists). Don’t forget to read the conclusion part in the end either. That is followed by the team (end user/employee) experience coming back to the reporting/following up part how tasks completion is being tracked. In this blog post I go through steps needed to create your hierarchy and prepare the tenant for Task Publishing and also how you create tasks lists and publish them. Teams are selected using a hierarchy and filters, that makes it easy to target these task lists to big number of teams at once – and follow up the progress how tasks are being assigned & completed. Target teams define by themselves who are responsible of those tasks and take care of marking them complete. ![]() In short: specific users can create and publish tasks lists to selected teams – and tasks are automatically added to target team’s Tasks (Planner) boards. Managers who are part of teams in the hierarchy between the local manager and the task list publisher can track assignment and completion of tasks, but cannot change anything. Task list publishing is how operations managers and other organization planners distribute tasks to the teams who perform the work. Each team receives one copy of the list, so local managers can assign tasks to their workers. If you’re a team manager, find out how to assign and track tasks in Teams. Each team gets its own copy of the list for assigning and completing tasks and tracking team progress. ![]() Microsoft defines Task Publishing very well in that Support article:Īs a Teams user who has been enabled for task publishing by your organization, you can create a list of tasks to send to any number of teams in your org. updated this post with task list housekeeping (unpublish, duplicate, delete) In this article I lay out how you can get started while following also the documentation presented here. The general info about Task Publishing can be found in here. Task Publishing was recently made available in Microsoft Teams. ![]()
0 Comments
Leave a Reply. |