Releases

Select multiple sticky notes and take action on them at a time. It is a great help when you're working with tons of sticky notes, right? As soon as more than one sticky is selected you can move them to another position, align them vertically or horizontally, or link them to sticky notes or team objectives. Brilliant, isn’t it?

A handy solution is to link sticky notes to Team Objectives that help to achieve the specific Objective. Instead of linking each sticky note to the Objectives one by one, you can do it all at once thanks to the multiple sticky note selection function. Then click on the Objective to see the associated notes highlighted.

It is now possible to work freely with the results filtered in the search bar. Edit or move the sticky notes, and when you're done, delete the filter criteria so that you can work in the full workspace again.

If you want to talk through certain sticky notes, be specific by sending your team members which sticky notes you are talking about. You can do this simply. For instance filter out sticky notes with a pending status that belongs to your Scrum Master. Copy the link of the search result from the URL bar and send it to the Scrum Master. Now he/she can see the exact sticky note you want to point to.

You will find a cleaner and more transparent renewed session selector after logging in. We have also revamped the navigation bar, which includes a new element called facilitation. From here you can access the timer and progress display.

Do you want to know which tasks still need time and which ones are not ready yet? When searching, filter by sticky notes with to-do and in-progress statuses. You will immediately see which tasks are still to be done.

Track the progress of your feature by hovering over the progress bar to see the status of the sticky notes in a mini report. ⚪ To Do | 🔵 In Progress | 🟢 Done.

Based on the status of your linked work items you can now easily track progress on your Objectives. You will now have an even better overview of the processes in your Program Increment.

To avoid unnecessary manual work, when the status of a user story changes, it is automatically updated back and forth between piplanning.io and other ALM tools like Jira, Rally or Microsoft Azure DevOps.

It is now possible to link User Stories to Team Objectives on the Team Board. Click on the link at the bottom of the sticky note you want to link, then select the desired Objective from the options listed.

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.