For teams that run on Microsoft Planner

Keep Planner. Add the portfolio.

Your teams keep working in Microsoft Planner. Onplana links their plans into one portfolio and adds what Planner does not have: a status for every plan, the dependencies between plans, the late milestones, and the open issues and risks, on one page.

Linking plans into a portfolio is on the Business plan and up.

Planner stays the place to work

Planner is where a team runs its own plan. What it does not give you is the view across plans that a PMO reports from. That is the part Onplana adds.

Stays in Planner

  • Tasks, buckets, labels, checklists and assignments, edited where your teams already edit them.
  • Planner owns each task: a change made there arrives in Onplana on its own.
  • Nobody moves tools, and nobody keeps two task lists up to date.

Added by Onplana

  • One portfolio holding every linked plan, with a status for each plan worked out from Planner's own dates and percent complete.
  • Dependencies between tasks in different plans, drawn across the plans on the portfolio's timeline.
  • Late milestones, dependencies at risk and the open issues and risks of every plan, each row linking to the item.
  • What you add in Onplana (dependencies, risks, issues, comments) stays in place when the plan syncs.

How linking works

1

Connect Microsoft

Connect your Microsoft account to Onplana with the Tasks and Groups permissions. Your organization may need an administrator to approve them once.

2

Pick the plans

In Import, choose Microsoft Planner, tick the plans (up to ten at a time) and name a portfolio, new or existing. Each plan becomes a project in that portfolio. Run it again and a plan already linked is not imported twice.

3

Planner keeps it current

Each linked plan keeps a Microsoft Graph subscription, so a change in Planner tells Onplana to read the plan again, and every sync recomputes the project's progress and dates. Integrations lists the linked plans with when each last synced, Sync now and Unlink.

4

Read the portfolio

Open the portfolio: the plans that need attention come first, then every plan with its status, and a Timeline with the dependencies between plans.

The portfolio reads as one page

What needs attention comes first, across every plan, and every row opens the item it names.

Status per plan

Green, amber or red for each plan, judged on its Planner tasks: their percent complete and their dates. A plan with no dates says Not rated, never on track.

Dependencies at risk

A task in one plan that waits on a task in another, listed when the task it waits on is past its finish or forecast to finish late.

Late milestones

Each plan's next milestone past its date, with a count of any others behind it.

Open issues and risks

The issues and risks logged against every plan in the portfolio, in one list. Every row opens the item it names.

One timeline

Each plan on its own line with the dependencies between plans drawn across them. A plan never moves the plan it waits on; it follows on its next recalculation.

What it does not do

  • It does not write to Planner. Change a task's title, dates, progress or assignee in Planner: the same change made in Onplana is replaced at the next sync.
  • Comments and files attached in Planner stay in Planner, because Microsoft stores them outside the plan.
  • A dependency between plans never reschedules the plan it waits on.

Comparing Planner and Onplana feature by feature? Onplana vs Microsoft Planner

Questions teams ask

Do our teams have to stop using Planner?▾
No. Teams keep working in Microsoft Planner. Onplana reads each linked plan and adds the portfolio above it: a status per plan, dependencies between plans, late milestones, and the open issues and risks across plans.
Can we edit a linked plan's tasks in Onplana?▾
Planner owns the task fields, so make those changes in Planner. A change in Onplana to a field Planner owns, such as the title, dates, progress or assignee, is replaced at the next sync. What Onplana adds to a task, such as a dependency on a task in another plan, a risk, an issue or a comment, stays, because each sync updates the same task in place.
How do Planner changes reach Onplana?▾
Each linked plan has a Microsoft Graph subscription. When the plan changes, Planner notifies Onplana and Onplana reads the plan again, then recomputes the project's progress and dates. Integrations shows when each plan last synced, and Sync now reads it straight away.
What does Onplana bring across from a plan?▾
Buckets become epics, tasks keep their title, start and due dates, percent complete, priority and description, checklist items become subtasks, labels become tags, and assignees are matched to your members by their Microsoft account.
Which Onplana plan do we need?▾
Linking plans into a portfolio, the portfolio page and dependencies between plans are on the Business plan and up. Onplana also has a Free plan, so you can look around first.
What happens if we unlink a plan?▾
The project keeps its current data, and changes in Planner stop arriving. Link the plan again from Import to mirror it again.
Where is Onplana hosted?▾
Onplana is hosted on Microsoft Azure. The portfolio page also opens inside the Onplana app in Microsoft Teams.

Keep Planner. Add the portfolio.

Create a workspace, connect Microsoft, and link the plans your teams already run. Linking into a portfolio is on the Business plan and up.

Already have an account? Open Import and choose Microsoft Planner.