Releases

Navigating between Teams and ARTs is now simpler with the new ART selector on team boards and a Team selector on ART and Solution Boards. Additionally, when you leave an ART and return, you’ll automatically rejoin as the same team you left, making it easier to pick up where you left off.

Now, when you sync sticky notes from Jira to piplanning.io, the assignee information is automatically transferred. This ensures that every team member can see at a glance who is responsible for each task, facilitating better coordination and accountability across your Agile Release Train. Enjoy a more connected planning experience.

The StickyNote Pro isn't just a new tool – it changes the way we work. It comes in many types and colors, all designed to fit your unique way of working. But no matter how you use it, its simplicity remains the same. Simplicity is what we're all about.

If you want to close the search but keep the filter active in order to work on the board, click on "Keep Filters & Close". To clear the filter, click on the X in the top navigation on the left.

The Plan Readout overview now also shows the iteration in which the work items linked to the team objective were planned.

The sticky note activity overview allows you to see what has happened to a sticky note since it was created. Who changed what and when. This helps with traceability.

Efficiently manage cross-ART dependencies with the ability to mirror them onto the Solution Planning Board. When a team faces dependencies with another team in a different ART, reflecting these dependencies at the solution level ensures clear visibility and facilitates easy tracking across multiple ARTs.

Discover a polished new look for sticky notes! Our revamped design places the navigation menu at the top, enhancing user experience. Effortlessly access essential functions tailored to the specific type of sticky note.

Introducing the power of swift copy-paste with multiple sticky notes at once! Enhance your workflow by seamlessly duplicating and transferring information across several sticky notes in one go.

In Draft or Final Plan Readout, you can review the key planning outputs (PI Objectives, capacity and load, risks) easily in a new dedicated space. It offers quick access and aids in the tight timebox. Moreover it allows Business Owners to assign Business Value for Objectives.

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.