Releases

Want to check if all dependencies are also linked to either a Feature or another Dependency, filter for “Unlinked” dependencies.

Thanks to the team-field sync with Microsoft Azure DevOps, when a team changes the text on a sticky note or moves it from one Iteration to another here will be automatically updated there and vice versa.

When you want to link a sticky note to an item and you click on "Link" on the sticky notes, you can search now among the linkable items. In the search bar, start typing the word you are looking for to filter the list. To make the items appear even neater, the sticky notes and Objectives are placed on two separate tabs.

You can choose which side the navigation bar should be on. If it's in the way because it's covering something, you can move it to the other side. Always to where it's most comfortable for you.

Want to take a closer look at an area on the Team Board? Right-click on the cell you want to inspect and select zoom to a region option. Now only that area is in focus on your screen.

Don't know which board you're on? You can always see the title of the board you are standing on at the top in the middle. In the case of the team board, you can jump to the other team's board from here.

Thanks to the team-field synchronization with Jira, when you change the text on a sticky note or move it from one team to another within the same Iteration here will be automatically updated there and vice versa.

It's easier than ever to connect sticky notes with Objectives. Click on it to activate the sticky note and just drag & drop the string to the Objective you want to link.

Highlight the items that are linked to each other! This works back and forth. Click on the sticky note to see the linked Objectives or click on the Objective to see the linked sticky notes.

In addition to English, you can now set Spanish or Japanese as your preferred language. Choose the language under your profile.

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.