Connecting Planner tasks to employee goals/OKRs - anyone figured this out?
My manager wants us to tie our daily Planner tasks back to our quarterly OKRs but theres no native way to do this. I spent a couple hours trying to set up a Power Automate flow that updates an Excel tracker whenever a Planner task gets completed but it feels hacky. Is there a cleaner way to connect what people are actually doing in Planner to higher level goals?
2026.02.20 - Planner UI update is worse
The UI changes to Planner within the latest Teams desktop app update (version 26032.208.4399.5) has regressed in its functionality and is worse than before. Previously, all of the contents of an item in the Planner were visible at the same time. Now I have to tab between Task Details, Attachments and Checklist, and am unable to view these at once, which has become a critical workflow for me. It is extremely irritating, as I've developed a workflow around how Planner was presented (which was that everything within a task was visible at once), and now it has been compartmentalised. Please unwind this - it is a regressive update and provides less information and requires more interaction to work through the detail of a task.
Timeline zoom
Hello, Is there a way to lower the zoom level in the Timeline view to less than 1 week? I have a couple projects with multiple dependent task per day but if I use the maximum zoom level in the Timeline view I don’t get a good overview of the different task in for example a 4 day period. I was expecting a Gantt chart like view, like what you have in Microsoft Project, in where you can zoom to a minute level granularity even.Can I delete or reorder the un-used labels in Planner?
I noticed that there are a lot more color labels in Planner and picked the brighter colors that are lower in the drop-down list. When I use "Group By Labels" to view my planner according to these color labels, my tasks are listed way to the right end side of the board, with a bunch of empty color label columns I didn't use. I tried re-ordering and deleting those un-used color labels but I can't seem to find the features. This really defeats the purpose of adding all the new labels...
[BUG] msdyn_project silently renamed from "Plan/Plans" to "Project/Projects" in new environments
We need clarification from Microsoft on whether this is a bug or an intentional breaking change. Overnight and without any announcement, the msdyn_project table now ships with display name Project / Projects in newly provisioned environments. Dev and UAT environments provisioned a few months ago have Plan / Plans out of the box. All environments are running the exact same PSCore version: 1.0.163.730. The entity is as expected, marked non-renameable — read-only in the maker portal — so there is no way to align environments manually. Solution import from an existing environment (where msdyn_project = "Plan") into a newly provisioned Production environment fails with: 0x8004023B: Entity 44286cce-2389-4532-ac04-7a18a2818e9a is not a renamable entity. Hence Entity Display Name cannot be modified The only workaround — and why it is not acceptable It is technically possible to manually edit customizations.xml inside the solution ZIP before importing, removing the <DisplayName> node for msdyn_project. The import will then succeed, but Production will permanently show "Project" while Dev and UAT show "Plan" — a broken inconsistency across environments. More importantly, this is not how ALM is supposed to work. Developers should never have to manually patch solution artifacts to work around a platform-level inconsistency introduced silently by Microsoft. This is incompatible with automated CI/CD pipelines and unsustainable for any team managing multiple environments. The question for Microsoft Is this a bug or a planned change? If it is a bug: when will it be fixed, and is there a supported workaround in the meantime? If it is a planned change: why was it not communicated, and what is the supported migration path for teams with existing environments and solutions? [UPDATE]: After 3 attempts of resetting and reprovisioning the Production environment, msdyn_project finally came up with Plan / Plans — same process, same PSCore version each time. The behavior is non-deterministic. The only workaround currently available is to keep resetting your environment until you get lucky, which is not an acceptable answer for any type of deployment.
Planner tab missing from Teams channel only shows as separate app
Our users can no longer open the Planner in the Teams channel; they can only access it via the app. This has been the case for a short while now. Does anyone know of a fix for this, or is this how it’s supposed to work? It cannot be selected via apps.
New planner doesn't show a "schedule" view of tasks assigned to me from different plans
The new version of web-based Planner was enabled for me a few days ago, on November 17th. Apparently, I realized that one of the features I used is missing. At the "My Tasks" view, in the old version of Planner, one could choose to have different views, apart from the grid view. The most useful one for me was the "schedule" view, since I could see in one calendar, all assigned tasks from different plans/teams/projects. This functionality now seems to have been removed, and one can only see one separate schedule per plan.Planner Training
Will there be updated Planner training videos? My organization is new to utilizing MS project management apps (trying to provide this tool so our multiple internal users stay with our protected Share drive). I could use the training and then turn around to support our end users to enhance buy-in and willingness to try something new.Microsoft Project Service Core Jan 2026 Update locked Plans table
We recently noted the Microsoft Project Service Core was updated to 1.0.161.1772: This update has locked our Plans table, no changes are allowed to the forms and creating new columns is greyed out: We cannot make use of Planner in our model driven app (Planner Premium, non-default environment). After a new Plan is created, the user receives this message when opening the Plan: Two days ago we were in this version 1.0.160.2874): and everything was working as expected. Any guidance would be much appreciated as we are not sure if this is a permanent lock or once the update cycle is completed we will be able to go back to edit Plan forms and columns. Thank you in advance
