Changelog

January 17, 2025

Open

 

Open

New Features

• Support for changing organization structure with carrying over PIs: Changes in ‘My Organization’ now respect and transfer existing PIs where applicable.
  When moving an ART to a Large Solution, the ART retains its completed and current PIs, provided the current PI does not extend beyond any active PI of the Large Solution. The ART also becomes part of the Solution's planned PIs.
  If the ART is detached from a Large Solution, it will carry over its completed PIs from when it was part of the Solution, ensuring that relevant data in the reports is preserved.

• New Custom Project Permissions: This version introduces new project permissions for more granular control over access and editing of Agile Hive's Project Settings. The new permissions, ‘Administer Agile Hive Projects’ and ‘Manage Agile Hive Project Members’, allow specific users to manage these aspects. Additionally, the default Jira permission ‘Administer Project’ continues to provide access to most project settings within Agile Hive (refer to https://agilehive.atlassian.net/wiki/spaces/CLOUD/pages/998866948 for a more comprehensive overview).

• ‘Starred' Section in the Sidebar: Starred Jira projects within your company's organization in Agile Hive are now displayed in a dedicated section of the navigation sidebar, making it easier to quickly access the projects you work with most often.

Improvements

• Criticality filter for the Dependency Overview widget: The ‘Dependencies’ widget now comes with a filter to display dependencies based on criticality. Filtering works just like in Agile Hive Team Planning and Roadmap Boards.

• Introduce a more helpful error message for restricted Parent projects: If you lack access to a parent project (e.g., the superior ART), most data cannot be meaningfully displayed. Instead of causing a crash and returning an error 500, the system now suggests requesting access to the direct parent project when necessary.

Bugfixes

• Creating Iterations and Sprints with only having the ‘Manage PIs and Iterations’ permission on ART/LS levels: The newly introduced custom permission, ‘Manage PIs and Iterations’ (see Changelog archive (2024) | December 9, 2024: ‘Manage PIs and Iterations’ permission major Release), previously caused a bug when users had only this custom permission at the ART and LS layers, along with the ‘Manage Sprints’ permission for all underlying Team projects. Due to a misconfiguration, the mapping between Iterations and Sprints could not be saved. This release fixes the issue, ensuring that users with these permissions can now create PIs and Iterations as intended.

January 13, 2025

New Features

• beta ‘Improved Planning’ mode in Team Planning Boards: To prepare for the revamped experience of planning and displaying ART Feature swimlanes on Team Boards, some functionality is now available in early access. Users can enable this preview on any Team Board by using the toggle switch located in the top toolbar.
  When the 'Improved Planning' mode is activated, it severs the link between the Team Planning Board and the ART-level Roadmap. Consequently, only those ART Feature swimlanes that are tagged with specific values for the 'Assigned Teams' and 'Assigned PIs' Custom Fields will be displayed on the Team Planning Board.
  Learn more on the upcoming changes and how to prepare here: Changes to planning of ART Features for Teams (expected early 2025).

• Dynamically hide Agile Hive-specific interface elements in Jira views: In projects that are not set up in ‘My Organization’ within Agile Hive, interface elements of the app will no longer appear in Jira project views. This means the ‘View in Agile Hive’ navigation item, the ‘SAFe® Hierarchy’ option in an issue's ‘Apps’ menu, and the ‘Agile Hive’ context panel on the right-hand sidebar in Jira issue views will not be displayed. There will be no changes to projects that are included in ‘My Organization’.

Improvements

• Creating new issues by pressing ‘C' in Agile Hive views reflects current project context: When you press the ‘C’ button in any Agile Hive view, now the 'Create Issue' modal automatically fills in with the project context you have been working in. Additionally, the issue type you last created is preselected to streamline the process of creating new issues and align better with the standard Jira experience.

Bugfixes

• Long Team names in Team Boards did not wrap correctly: Fixed a bug where long Team names did not wrap properly in swimlanes on Team Planning Boards, leading to overlapping text labels or unintended line breaks.

• Removing parent issues that no longer belong to the hierarchy failed in Issue List view: Fixed a bug that prevented users from removing or editing the parent information of issues when the existing parent was no longer included in the project hierarchy defined in 'My Organization'.

• Team-level issues linked with deleted ART Feature not displayed in Team Planning Boards: Fixed a bug where Team-level issues linked to a deleted Feature at the ART level were not displayed on Team Planning Boards, despite being planned for the respective PI. These Team issues will now appear in the ‘Independent’ swimlane of the Team Planning Board.

• Broken link to manage quick filters in Team Boards & Roadmap Boards: Fixed a bug that blocked users from accessing the quick filter settings from Team Planning Boards and Roadmap Boards.

• Error code 500 when navigating to Reports and Planning tabs of Team-level projects within restricted ARTs: Fixed a bug where users received a 500 error code when attempting to access the Reports or Planning tab of a Team layer project linked to a restricted ART-level project.

• Error code 403 flashing when navigating to Agile Hive Jira Administration: Fixed a bug where users encountered a fleeting 403 error code when trying to access Agile Hive settings in the Jira Administration. This occurred because permission checks in the backend took longer than the user interface to load.

Changelog archive

For older changelog entries please refer to our archive: