A new "Assignee" field on sticky notes now allows you to assign users directly within the app. The assignee syncs seamlessly with Jira and Rally, displaying user IDs and enabling easy edits. This update enhances collaboration by linking ALM user assignments to piplanning.io.
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.
piplanning.io is now fully compliant with Section 508 and WCAG 2.1 Level AA accessibility standards! This update ensures an improved experience for all users, including those with disabilities, by enhancing keyboard navigation, screen reader support, color contrast, and more.
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.
piplanning.io now fully supports Jira's new "parent/child" link type, allowing admins to configure this standardized way of linking Features, User Stories, and other work items. This update streamlines project setup, enhances linking in the RTE Cockpit, and ensures a smooth experience for customers using the Jira Integration.
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.
Prepare New PI: Retain the original PI configuration while updating teams, iteration names, and mappings. Duplicate This PI: Create a copy of the PI with the option to update team compositions, typically used when teams change before PI Planning begins.