A collaborative workspace app in Microsoft 365 designed to help teams co-create, stay organized, and work together in real time across apps and devices.
Loop Component Name Not Displayed in Other Microsoft 365 Apps (Planner, To-Do, Outlook)
Dear all
In our team, we extensively use Microsoft Teams for our work processes. Since we manage numerous small tasks across multiple workflows involving various people, we rely heavily on the Loop component in Teams. Specifically, we use the task list feature within Loop to assign and track tasks across the team.
However, we’ve encountered a recurring issue: although we name each Loop component for better organization, the assigned tasks in related apps such as Planner, To-Do, or Outlook do not display the specific name of the Loop component (while it is correctly displayed in Teams, and also in the Files section of the Teams channel). Instead, they are generically labeled as "Loop-Absatz".
This makes it very difficult to identify which Teams conversation or Loop component a specific task belongs to. This issue creates confusion, especially in our workflows where multiple Loop components and tasks are in use simultaneously.
To illustrate the problem, I have attached three screenshots (in German, as we use Microsoft Teams in German):
- A Teams view with the named Loop component.
- A Planner task where the Loop component name is missing.
- An Outlook task notification displaying "Loop-Absatz" instead of the custom Loop name.
The issue has been highlighted with markings for better visibility.
Is this a known bug? If so, are there plans for a fix? It would greatly enhance usability if the custom Loop names could appear consistently across all Microsoft 365 apps.
Thank you for your attention to this matter, and I look forward to your response.
Best regards,
David Gruber
Microsoft 365 and Office | Loop | For education
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.