![]() ![]() ![]() This makes sense because the Loop task object is simpler and doesn’t support the same properties as Planner does. The Microsoft support article says that tasks in task list “ stay in sync with a plan in Planner.” From this we understand that the roster container is independent of the Loop component. ![]() While the basics of tasks are synchronized (including new tasks added in Planner), don’t expect all the changes made in Planner to synchronize back to the Loop task list component. Clicking the Loop icon to the right opens the Loop component using the same browser interface as used if you open a Loop component from OneDrive for Business.įigure 3: Updating a Loop task through Planner The tasks listed in the Loop task list are present and assigned to the right people. Working with Roster Containers in Plannerįigure 2 shows the plan after opening it in Planner. In this context, the planner roster container holds the set of Loop tasks, the roster (of users authorized to work with the plan) are those who share the Loop component, and the tasks in the container are those created in the Loop component. The Microsoft Graph defines a planner container resource and notes that two types of planner containers are currently supported: plans contained in a Microsoft 365 group and plans contained in a planner roster. It looks like being able to open the tasks created in a Loop task component in Planner is the outcome of that work. In the past, Microsoft talked about roster containers (plans without Microsoft 365 groups) and a potential integration between lightweight plans and fluid (now Loop) components. The big change here is the option to “Open in Planner” available from the menu at the top of the task list. Figure 1: A Loop task list component in an OWA message ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |