/
Changelog

Changelog

 


January 13, 2025

New Features

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: