Releases

We have now officially released the synchronization between Microsoft Azure DevOps. It is a real-time synchronization with your piplanning app boards. What does this mean? For example, if you create a user story with a summary on the Team Board and enter a Story Point value, this is also reflected in Azure DevOps. Conversely, if you change the iteration in Azure DevOps, for example, it will also be updated in the piplanning app. Find out more and click on "Lean more".

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

For a long time we collected feedback and worked on it. Now they are finally here. We call them Collaboration Canvases. As the name suggests, these are interfaces that are flexible for all kinds of collaboration, be it retros, problem solving sessions, Scrum of Scrums, you name it. We already offer a wide range of backgrounds. If you are still missing one, let us know.

In the sticky overview on the Team Board you can now adjust the size of the sticky just like the Objectives.

The date format now adapts to the format based on the country setting you have in Chrome.

Between blue, all is well and red, you have an overload you can now also set if it should highlight with a yellow background that you soon reach the capacity limit. In the settings you can put in at what percentage the highlighting should trigger.

In the settings you can now set that the invisible links are always displayed on the Team Board and Program Risk Board.

If you long-press on a sticky note it will show you the link above the grayed out sticky notes.

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

Our first step into the reporting field. Now you can find out on team level how much is planned for which area based on iterations or the whole team.

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.