Start here · Version
What's in 2.5.2
PMO Assist 2.5.2 builds on 2.5.0, the release that brought dashboards, account roles, portfolio health and delivery reports. This page says what came after it, and what is not in the product yet, so nobody promises it to a client.
New in 2.5.2
Own
Account owners
A leader holding the Account owner template creates accounts and becomes the Owner of each. They see and run every programme and project under their accounts, and create and manage the people they hire, without seeing the rest of the organisation.
Run
The account Owner role
Above Admin on an account. An Owner works on every project under the account as its lead, without being added to each one. Archiving and deleting a project stay with that project's own owner.
Hire
Account Product Manager
A designation an Account owner can give. With the Manager role on the account, that person creates projects under that account and nowhere else.
Guard
Designations can't over-grant
Giving someone a designation gives its template. Now the giver must hold everything that template carries, so nobody hands out more access than they have.
Look
Dashboard and theme
One pinned toolbar on the dashboard, panels that fit what they hold, deeper dark mode, and Ctrl Shift L to change theme from any page.
Name
"Work item" everywhere
The project's Issues page is now Work items, and every button and message says work item. Links such as /issues/101188 still work.
Fixed in 2.5.1
- Weekly reports no longer email the team unasked. Email the team is off by default; the app still notifies people.
- Viewers never see work items they may not read, and links only go to pages the reader can open.
- Editing a resource saves again, half days of leave can be requested on any date, and logging time by start and end works as expected.
- Imported sprints keep their Azure DevOps dates.
- A delivery report's Publish waits until something has been written.
Not in the product yet
Earlier material described some of these as coming soon. Please don't present them as available.
| Not yet | What to say instead |
|---|---|
| A screen to enter a project's budget | Budget burn works today for dedicated capacity, from allocated hours. For fixed price and time and materials it shows spend against a budget only where one has been recorded. |
| Contract value, bill rates and margin forecasts | Each allocation carries a cost per hour, and the project's Team cost shows planned against actual cost. Revenue and margin are not calculated. |
| Budget as a health dimension | Health rates schedule, staffing and flow. Time and materials and managed service projects are judged on flow for now. |
| Client sign-in | Clients read what delivery shares: a public deck link, a delivery report link or a PDF. |
| Company single sign-on | People sign in with their work email and a password they choose from the invitation. |
| Import from Jira | Azure DevOps import is available; spreadsheets import people. |
The Outcomes tab and its outcome register, the AI brief at the top of the dashboard, and the Team lead, Portfolio manager, HR administrator and Workspace admin templates no longer exist. Their jobs moved to milestones and releases, the dashboard panels, and the Delivery manager, Account owner and Workspace manager templates.