Releases

With "control" and the key "4" you can jump through the team boards. Very helpful if you want to get a quick overview of the different team boards.

When you are on the team board, you can simply press "Control" and "O" or "Command" and "O" on your keyboard and it will open the Objectives overview.

When you are on the PI Objectives Overview, you can use the arrow keys to jump through the objectives. The arrow keys on your keyboard also work for this.

To get to the PI Objectives Overview, you can simply press key "6".

In the Objectives you can now only make line breaks by holding down the "SHIFT" key.

Learn in this video what we released in October 2020 for the Cloud piplanning app.

In the search, you can now also highlight stickies that don't have stickers.

Now it always remembers to which sticky you last linked another sticky. So you can quickly link to the same sticky with your "Return" button.

If you have mirrored a Risk between the Team Board and the Program Risk Board and you move it to another ROAM area on the Program Risk Board, it will be updated directly on the Team Board.

Now the team name is no longer included in the text of the sticky note as before, but nicely listed separately below the summary.

Load Warning and Capacity Limit Theshol are now configurable in the RTE Cockpit under the Team Board configuration

PI-Admins can now be assigned to specific ARTs and Solution Trains (STs), extending their permissions to manage teams, ARTs, and STs based on their assignments. This change enhances control over visibility and editing capabilities in the RTE Cockpit. Important: When a user’s role is modified, the system retains their ART/ST associations but adjusts permissions accordingly. Please be aware that this is a breaking change, and further guidance on managing these new permissions will be provided in our documentation.

Helping organizsations meet compliance needs, admins can optionally adjust an inactivity timeout in the cockpit settings after which users get automatically logged out. This functionality detects mouse and keyboard activity, ensuring that only active sessions remain logged in.

ART backlog issues in Jira can now be filtered by additional field types beyond labels, these are FixVersion, Component, Single-select (customfield), and Multi-select (customfield). This does simplify your configuration and providing greater flexibility in synchronizing your ART backlog.

You can now setup your team by mapping Microsoft Azure AD groups directly to teams using OIDC. This feature allows for efficient team management and synchronization with your organization's AD structure, making user and team onboarding quicker and more consistent.

We’ve updated the login behavior for environments with SSO enabled. When SSO-only is active, username and password options are hidden, and user management is streamlined, allowing admins to add users via team assignments but removing password reset options. When SSO is off, login fields for username and password, password resets, and user invitations via email are available, offering greater flexibility in user management.

piplanning.io now supports Azure DevOps (ADO) instances (on-prem) using XML process templates, enabling seamless bidirectional sync of work item statuses. By refining the integration to exclude unused properties like custom rules, this update improves compatibility with XML process templates while maintaining clear logging of any API errors due to custom rules for admin visibility in ALM Events.

Admins can now export a comprehensive list of all users within their company as an XLSX or CSV file. The export includes user details such as ID, email, name, role, teams, last login, and SSO linkage, supporting compliance needs with easy access to user data.

The precond-team and depend-team you add on dependencies are now part of the xlsx session export.

You can now synchronize the team-field (project) between Rally and piplanning.io ART-level sticky notes.