Page Comparison

...

...

November 14, 2024

Improvements

• Highlight completed Sprints in Team Planning Boards: To align with Jira, Agile Hive only permits changes in Team Planning Boards for Iterations linked to a Jira Sprint that hasn't been marked as completed. To help users easily identify Iterations connected to completed Sprints, Agile Hive now displays these Iterations in a different color (grey instead of purple) on the Team Planning Board.

• Provide information on unplanned Team-level issues for Features in ART Planning Board: When reviewing the estimated delivery timeline of ART-level Features for a PI, it can be challenging to identify if any work within a Feature is still unplanned by the Teams. Agile Hive now simplifies this by highlighting any unplanned Team-level issues hierarchically linked with ART Features on the Board, which could potentially delay the Feature's delivery. To view a list of all unplanned Team-level issues linked to a Feature, simply click the warning icon () on the Feature’s issue card in the ART Planning Board.

Bugfixes

• Incorrect display of PIs containing no Iterations: Fixed a bug that caused PIs without any Iterations to display incorrectly in the Team Planning Board view.

• Hide flags on loading errors within issue contexts and panels: Fixed a bug that caused error flags to appear in multiple Jira views whenever specific Agile Hive UI elements were present. This issue mainly affected projects not added to Agile Hive, as they lacked relevant data to display.

November 06, 2024

Improvements

• Automated background updates of calculated Custom Fields: Updating the value of a calculated Custom Field in Agile Hive is now more reliable and consistent.

• Update of internal libraries (technical foundation): Improved product stability and security by updating a bunch of internally used libraries to the latest version.

Bugfixes

• Display indicator for ‘Owning Team’ in all issue cards on ART level: Fixed a bug that prevented the Owning Team indicator from displaying consistently alongside the related issue in Agile Hive board views.

• Sprint Mapping settings not working for Team-level projects that include Kanban boards: Fixed a bug where Sprint Mapping settings were not functioning correctly for team-level projects with Kanban boards. The bug caused Sprint Mapping to fail in certain projects that included at least one configured Kanban board.

• Display correct values for ‘PI Involvement’ column in Issue List: Fixed a bug where the 'PI Involvement' column in the Issue List appeared empty, despite the corresponding Custom Field being set for the Jira issue in Agile Hive.

...

• ART Planning Board: Team level issues are being displayed with non-dependency links to the ART parent: An issue was fixed, where Team level issues were displayed on the ART Planning Board, even though the issues were not linked with another issue type, than the configured Agile Hive Dependency Link Type.

October 10, 2024

...

Improvements

• Compact issue card layout in all boards: To give you a clearer overview of the big picture in any of Agile Hive's board views, we've introduced a compact issue card layout. You can easily switch between the compact and extended layouts using the new 'View Settings' dropdown in the board toolbar.

• Optimize column width for ART PI Overview Report widget: The ART PI Overview widget now more effectively utilizes the available horizontal space to display essential information, such as the issue key and full summary, for every ART-level issue.

Bugfixes

• Quick Filters in ‘Unplanned Issues’ sidebar of Roadmap Boards do not work as intended: Fixed a bug where the quick filters in the ‘Unplanned Issues’ sidebar of Roadmap Boards failed to filter down the list of issues after applying one or more filters.

• Quick Filter options in ‘Unplanned Issues’ sidebar of Roadmap Boards do not refresh: Fixed a bug where the quick filters in the ‘Unplanned Issues’ sidebar of Roadmap Boards did not refresh after clicking the ‘Update Data’ button for the board.

...

• Visualize dependencies with Team-level issues in ART Planning Board: The ART Planning Board now includes dependencies with Team-level issues that are linked to ART-level issues scheduled for completion in the selected PI. This provides users with a clearer view of potential blockers that could lead to unexpected changes in the planned delivery dates of scheduled Features.
  To add a dependency between a Team-level issue and an ART-level Feature to the ART Planning Board, simply create a new Jira issue link between them using the dependency link type defined for Agile Hive in your site.

Bugfixes

• Agile Hive Screen Schemes cannot be created automatically during initial setup: Fixed a bug that prevented Jira administrators from creating the Screen Schemes provided by Agile Hive during initial setup, despite all required Screens being successfully created before.

• ART-level PI Objectives cannot be displayed by users with insufficient Team-level permissions: Fixed a bug that prevented users from displaying ART-level PI Objectives in Reports if they lacked sufficient permissions for all Team-level projects within the respective ART.

...

• Replace custom Agile Hive Administrator management with global Jira permissions: Replaces the current Agile Hive Administrator Groups with global Jira permissions. This is the first step towards a more granular permission management. Adding Admin-Groups in the Agile Hive settings is now disabled, and Admin-Group settings are set to read-only with a clear notice. The Agile Hive Administrator permission allows users to manage key aspects of Agile Hive, including editing the organizational structure, creating Program Increments (PIs), and configuring project-level settings.

Bugfixes

• Fixes an error in Reports when selecting a planned PI without iterations: Fixed a bug that caused a 500 error when attempting to access the Agile Hive Report for a PI without any Iterations.

...

• Manually select primary Jira board in Agile Hive Project Settings: This allows Agile Hive Administrators to set the primary Jira board for projects with multiple boards, accessible in Agile Hive Project Settings under a dedicated tab. The selected primary board will be used for creating new sprints and providing quick filters within board views. This functionality is especially useful when working with projects that contain more than one Jira board.

Bugfixes

• Issue still appears in the backlog after being moved to the board: Resolves an issue where an item remains in the unplanned issues sidebar after being dragged and dropped onto the Team Board or Roadmap.

• Roadmap Board: 'Update Data' does no longer refresh Milestone information: Fixes an issue where the 'Update Data' button on the Roadmap Board did not refresh Milestone information. Milestones now update correctly without needing a full-page reload.

• Roadmap Board: JQL filter not being applied on 'Enter': Fixes an issue where JQL filters on the Roadmap Board were not applied after pressing 'Enter.' Users can now apply JQL filter queries directly by pressing 'Enter' without needing to click the 'Update data' button.

• Issue List: Cannot set / edit parent via inline edit: Fixes an issue where setting or editing an issue's parent via inline editing did not save the selection. The selected parent issue is now correctly saved when using inline editing in the issue list.

...

• Quick Filter for ART Parents in Team Planning Board: A new quick filter has been added to the Team Planning Boards, allowing users to filter the board by a single ART-level parent issue and all of its child issues. The filter applies across all teams within the ART in this view simultaneously.

August 27, 2024

Bugfixes

• Exclude Sub-tasks and other unsupported issue types in ART Planning Board: Fixed a bug in certain Agile Hive setups where Team-level issues were mistakenly interpreted as ART-level Features and appeared in the ART Planning Board. This occurred because Sub-tasks were not excluded in the default filters of the ART Planning Board, a problem that has now been corrected.

• ART PI Overview Report widget falsely displayed issues in ‘Issues with restricted parents’ section: Fixed a bug that caused the ‘ART PI Overview’ widget in ART-level Reports to incorrectly display issues under the ‘Issues with restricted parents’ section, even though they had no restrictions. The widget filters have been adjusted to ensure that ART-level issues are now displayed in the correct section of the Report widget.

August 21, 2024

Bugfixes

• Exclude Team-level issues in a ‘Done’ status from triggering a warning in the ART Planning Board: Fixed a bug that caused the ART Planning Board to incorrectly display a warning, indicating that not all connected Team-level issues were planned for a PI, even when those issues were already marked as ‘Done’ and would not obstruct the delivery of the ART Feature.

• Incorrect redirects when navigating from Team-level to Solution Train or Portfolio-level views: Fixed a bug that caused users to be redirected to incorrect views or dead-ends when navigating from a Team-level view in Agile Hive to a project at the Solution Train or Portfolio level.

August 16, 2024

Bugfixes

• Explicitly load issues with all required fields: Fixed a bug that occasionally occurred when required Jira standard fields were renamed or migrated from Server/DC with different naming conventions, causing the Agile Hive Burnup charts to fail in displaying 'Burned SP' in the Reports. Agile Hive will now explicitly load the complete field configuration for any issue, ensuring all necessary data is available to accurately visualize Burnup chart information.

August 14, 2024

Improvements

• Optimized calculation of Velocity in Team and ART-level Reports: The Velocity Report widget has been enhanced to more effectively meet users' needs regarding completed, current, and future PIs. Additionally, the improved calculation method should lead to fewer warnings and errors in the Velocity Report widget.

Bugfixes

• Issue type mappings in Agile Hive project settings cannot be emptied: Fixed a bug that previously prevented Agile Hive Administrators from clearing issue type mappings for individual features within the project settings. Administrators can now easily clear the issue type mapping for any Agile Hive features that are not in use.

• Restricted project displayed in Team Planning Boards: Fixed a bug where Team-level projects were visible on Team Planning Boards to users without the 'Browse project' permission for those projects. Now, projects for which users lack sufficient permissions are properly anonymized.

• Toolbar alignment and default sorting of Issue List: Fixed a bug where the JQL filter in the redesigned Issue List view was incorrectly aligned to the right instead of the left. Additionally, we updated the default sorting of the Issue List view to 'ORDER BY issuekey DESC'.

...

• Issue List sorting and filtering: We have upgraded the technical foundation of Agile Hive’s Issue List view and are pleased to announce that sorting and filtering (via JQL) are now available for projects at any SAFe® layer.

Bugfixes

• Text not properly truncated in issue cards: Fixed a bug where text labels on issue cards were not properly truncated, which could cause overlaps with other interface elements.

• Duplicate ‘Issues without parent’ row in ART PI Overview Report widget: Fixed a bug that caused a duplicate 'Issues without parent' row in the ART PI Overview Report widget for users lacking 'Browse project' permissions for some of the Team projects within the respective ART. Now, Agile Hive displays a dedicated 'Issues with restricted parent' row in these cases.

• Duplicate Sprints after recreating missing Jira Sprints via Iteration Overview Team Report: Fixed a bug that caused duplicate Sprints to be created via the Iteration Overview Team Report widget if a Sprint was missing from one of the selected PI’s Iterations. The Report widget now updates after a Sprint is created, preventing the creation of duplicates.

• Incorrect data in ‘SP burned’ Report widget for Iterations with missing Jira Sprint mapping: Fixed a bug affecting Team-level Reports when one or more PI Iterations were not mapped to a Jira Sprint. The 'SP burned' widget in the Team Report incorrectly displayed a non-zero value for burned Story Points despite no Sprint being available.

August 2, 2024

Improvements

• Smoother Drag & Drop of issue cards in Team Planning Boards: The performance and usability of dragging and dropping issue cards in Team Planning Boards have been enhanced to offer a smoother and more convenient user experience.

Bugfixes

• Incorrect Forecast in ART Burnup Chart: Fixed a bug where the forecast line in the ART Burnup Chart was incorrectly calculated. Previously, the forecast was calculated based on the average velocity of the teams within the ART, instead of providing an aggregated forecast for all teams of the ART.

July 24, 2024

Improvements

• ‘Today’ marker in Team Planning Boards: Team Planning Boards now include a 'Today' marker, providing a clearer view of the timely progress of the current iteration and PI.

• Performance improvements: Enhanced the overall performance and usability of the ART Planning Board and Team Planning Boards by optimizing data loading as well as the technical foundation in the codebase.

July 16, 2024

Bugfixes

• Milestones slightly misaligned in Roadmap Boards: Fixed a bug with the visualization of Milestone icons in Agile Hive Roadmap Boards, ensuring they now appear accurately on their planned dates.

• Error when adding or removing child issues in SAFe® Hierarchy issue panel: Fixed a bug that caused an error when attempting to remove the only child issue of an ART-level Feature. Additionally, this error prevented the addition of new child issues afterward.

...

• Issue List displays additional Agile Hive fields: The Issue List in Agile Hive now includes extra custom fields specific to the SAFe® layer configured for the current project. This allows users to easily view PI-related information for a greater number of issues simultaneously. Additionally, it offers a clear overview of the Teams contributing to specific issues within an ART.

  • Status
    colour Red title ART

    Teams Involved, Owning Team, PI Involvement, Assigned PIs

  • Status
    colour Purple title Team

    PI Involvement, Assigned PIs

Improvements

• Placeholder elements in ‘My Organization’ in case of insufficient user project permission: The ‘My Organization’ view in Agile Hive now shows a placeholder element for projects where the current user lacks sufficient Jira permissions (e.g., missing ‘Browse projects’ permission). This helps identify potential misconfigurations and allows Jira and project administrators to address the issue.

Bugfixes

• Team-level Report widgets utilized different data points: Fixed a bug where Team-level Report widgets used different data points for calculating their respective metrics. This issue could have caused inconsistent values for the same metric across various widgets, which should now be resolved.

• Incorrect Forecast in Burnup Charts when no historical velocity data is available: Fixed a bug in Burnup Charts that caused an incorrect forecast when no historical velocity data was available. Burnup Charts now use the velocity data from the current PI when no historical velocity data is available.

• Current day data point in Burnup Charts does not update correctly: Fixed a bug that prevented the data point for the current day from being properly updated in Burnup Charts.

July 3, 2024

Improvements

• JQL Search Suggestions for Risk ‘Exposure’ fields: When using the 'Exposure' or 'Residual Exposure' Custom Field of Agile Hive within a JQL search, Jira will now automatically suggest field values for your query. This enhancement simplifies and streamlines the process of searching for issues based on these fields.

• JQL Search Suggestions for ‘Assigned PIs’ field: Similar to the 'Exposure' fields, we have also added search suggestions for JQL searches involving Agile Hive’s 'Assigned PIs' Custom Field.

• JQL Search Suggestions for ‘Owning Team’ field: Similar to the ‘Exposure' and 'Assigned PIs’ fields, we have also added search suggestions for JQL searches involving Agile Hive’s 'Owning Team' Custom Field.

Bugfixes

• ‘An error occurred’ when displaying ART PI Overview Report widget: Fixed a bug that caused an error message to appear when displaying the ART PI Overview widget in ART-level Reports on larger instances of Agile Hive.

June 28, 2024

Bugfixes

• Too many redirects when accessing Portfolio and Solution Train-level projects: Fixed a bug that resulted in an infinite number of automatic redirects when users attempted to access a Portfolio or Solution Train-level project in Agile Hive.

...

• ART Planning Board: Get a comprehensive view of the estimated completion dates for all your ART-level Features with the all-new ART Planning Board. By factoring in the PI plans of all teams contributing to an ART, Agile Hive now offers completion date estimates. During PI execution, monitor the ART Planning Board to receive updates on Features that may be delayed, potentially impacting important Milestones. Additionally, Agile Hive provides information on the Owning Team for each Feature, enabling you to easily address any impediments along the way.
  For more information, please refer to our knowledge base article at ART Planning Board.

Improvements

• ART PI Overview Report widget includes Team issues without parent: ART-level Report widget ART PI Overview now also considers Team-level issues that are not hierarchically linked to an ART Feature. This results in the Report widget providing more accurate metrics that consistently add up across all Report widgets.

Bugfixes

• Users cannot empty ‘Owning Team’ field: Fixed a bug that prevented users from clearing the 'Owning Team' Custom Field. Users can now once again empty the field or modify its value as needed.

• Editing of Roadmap Planning fields in Agile Hive issue context not working: Fixed a bug where the Roadmap Planning fields in the Agile Hive issue context were not accepting user input, preventing users from editing this information in the Jira Issue View.

June 12, 2024

Bugfixes

• Agile Hive Custom Fields timing out: Fixed a bug that resulted in a couple of Agile Hive Custom Fields timing out when loading Jira issue view. While we’ve been able to fix the issue for the time being, we invite you to vote for also fixing it in the underlying Atlassian Forge framework: https://ecosystem.atlassian.net/browse/FRGE-1422. Thank you!

...

• ‘PI Involvement’ Custom Field for ART-level issues: The Agile Hive Custom Field ‘PI Involvement’ has been extended to include ART-level issues, in addition to its existing availability for Team-level issues. This update assists the Product Management of an ART by providing visibility into when Teams are working on a Feature and which PIs have Stories planned for ART-level issues. Moreover, the ‘PI Involvement’ field for ART-level issues integrates the ART Roadmap plan, offering a consolidated view of both the roadmap plan and the actual PI planning of the involved Teams.
  Adding this functionality required adding new capabilities to the app’s scope resulting in this version being considered a major release (13.0.0) by Atlassian. Please refer to Upgrading and Versioning for more information on versioning of Cloud apps.

Improvements

• Display all Team-level child issues at once for an ART issue in SAFe® Hierarchy panel: In the 'SAFe® Hierarchy' panel of the Jira Issue View, when examining the Agile Hive Issue Hierarchy of issues on the ART level, we now show all Team-level child issues. This enhancement allows for better tracking of all Teams involved in an ART issue and provides a more detailed view of the status of work to be delivered by these Teams.

Bugfixes

• PI dates off by two days when creating new PIs: Fixed a bug where users with a large UTC offset experienced newly created PI dates being incorrect by up to two days after creation.

• Roadmap not properly displaying planned PIs: Fixed a bug where the Roadmap Board failed to show all PI indicators when there were two or more PIs in a planned state.

May 31, 2024

Bugfixes

• Burnup Chart for PIs with 5+ Iterations: Fixed a bug that resulted in the Burnup Chart not updating correctly for PIs with 5 or more Iterations.

...

• New ‘Critical Dependencies’ widget for ART & Team level: Reports for projects at the Team and ART level now include a new widget that presents an aggregated count of unresolved critical dependencies within the current project for the selected PI. For more detailed information on these dependencies, the 'Dependency Overview' widget offers additional details.

• ‘Teams Involved’ Custom Field for ART-level issues: The 'Teams Involved' Custom Field is now available for ART-level issues. This feature offers a comprehensive view of all the teams involved in contributing work to the specific issue at the ART level. The information about the involved teams is sourced from the hierarchical Agile Hive issue links, which can be managed through Agile Hive's 'SAFe® Hierarchy' panel in Jira's issue view.

• ‘Owning Team’ Custom Field for ART-level issues: The 'Owning Team' Custom Field is now available for ART-level issues. Individuals operating within an ART can utilize this field to store the team accountable for the specific ART-level issue. This data will subsequently be utilized in the forthcoming ART Planning Board, along with other Agile Hive features.

Bugfixes

• Drag-and-drop of issues in the ‘Independent’ swimlane in Team Planning Boards: Fixed a bug that adversely affected user experience while planning issues in the 'Independent' swimlane of Team Planning Boards. When dragging and dropping issue cards within that swimlane, users may have encountered poor performance or even errors.

• Minor visual glitches in Report widgets: Fixed two minor visual bugs that were causing Report widgets 'ART PI Objectives' and 'Team Iteration Overview' to be displayed incorrectly.

...

• New ‘Team Burnup’ Report Widget: Reports for projects at the Team level now feature a new widget that provides a graphical representation of a Team's PI progress compared to the plan. The ‘Team Burnup' widget visualizes total workload, progress (Story Points burned), and a forecast specifically tailored for the selected PI. For more information on this widget please also see https://agilehive.atlassian.net/wiki/spaces/CLOUD/pages/607617051/Team+Reports#Burnup-Chart.
  Please note that the Burnup Chart data is not retrospectively calculated for completed PIs and days already passed in the current PI as of today. This may cause the lines in the chart to jump from 0 to their current values for PIs that are already in progress.

Improvements

• Retain selected PI when switching between Agile Hive views: When switching between views in Agile Hive, the selected program increment (PI) is now retained as a URL parameter. This enhancement prevents users from having to repeatedly re-select the PI for every view and enables seamless navigation within Agile Hive. Moreover, it facilitates sharing direct links to specific views in Agile Hive, automatically redirecting recipients to the correct PI.

• Date Range Picker for creating new PIs and Iterations: Setting up new PIs and Iterations has become easier than ever! Agile Hive Administrators now have the convenience of using a Date Range Picker to select PI / Iteration Start and End Dates, eliminating the need to manually select each date with an individual date picker.

Bugfixes

• Capacity in Team Planning Board fails to refresh upon pressing the 'Update Data' button: Fixed a bug that caused Capacity and Load not to update in Team Planning Boards when using the ‘Update Data’ button.

• Incorrect color code for ‘Load vs. Cap’ Report widget: Fixed a bug that caused the 'Load vs. Cap' Report widget to not display information using the correct color code.

...

• Quick filters for Unplanned Issues sidebar in Team and Roadmap Boards: Unplanned Issues in Roadmap and Team Boards can now be filtered to only display what's truly important, allowing for better focus. Agile Hive automatically incorporates the quick filters configured for the primary Jira board in that project (currently, this is the board with the lowest board ID). Users can apply multiple quick filters simultaneously and also utilize the search bar to conveniently locate specific issues.
  Adding this functionality required adding new capabilities to the app’s scope resulting in this version being considered a major release (12.0.0) by Atlassian. Please refer to Upgrading and Versioning for more information on versioning of Cloud apps.

Improvements

• Roadmap Board refreshes automatically after setting Start or End Date for Unplanned Issues: Agile Hive now automatically updates the Roadmap Board when users make changes to the Planned Start or End Date of an issue using the Jira issue modal. This simplifies roadmap planning and ensures users always have access to the latest data.

• Improved error messages for some Report widgets: We have enhanced the error messages for various Report widgets to provide more precise descriptions of potential issues that may arise.

Bugfixes

• Server error when changing an issue’s assignee in Issue List: Fixed a bug that resulted in a server error, which may have occurred when changing the assignee of an issue via Agile Hive Issue List.

• Dates in Milestone Overview Report widget one day off: Fixed a bug that caused Milestone issues to be displayed incorrectly in ART reports, showing a one-day discrepancy compared to the same Milestone displayed in a Team-level Report.

April 16, 2024

Improvements

• Knowledge base link in ‘SAFe® Hierarchy’ issue panel for projects not added to Agile Hive: The 'SAFe® Hierarchy' issue panel, now included with Agile Hive, not only provides a text hint on how to add projects to Agile Hive but also features a knowledge base link.

• Refresh ‘Business Value Delivered’ Report widget after creating a new Objective: When creating a new PI Objective from the Reports page, the 'Business Value Delivered' widget will now automatically refresh to display the updated information of the newly added Objective.

• Adjusted conditions for displaying a warning in ‘Story Points Burned’ and ‘Load vs Cap’ Report widgets: The warning associated with the Report widgets 'Story Points Burned' and 'Load vs Cap' will now only appear for issues of types that are capable of having a Story Point estimation.

Bugfixes

• ‘Update Data’ for Issue List results in infinite loading screen: Fixed a bug that caused an infinite loading screen when 'Update Data' was pressed in the Issue List view.

• ‘Update Data’ for completed or planned PIs displays data of current PI: Fixed a bug that caused Agile Hive views to display data from the current PI instead of the selected completed or planned PI after pressing ‘Update Data’.

• ‘Update Data’ did not reset timer after switching to another view: Fixed a bug where the timer of the 'Update Data' button was not being reset after switching to another Agile Hive view.

• Visualization of tooltips broken for issue cards in Team Planning and Roadmap Boards: Fixed a bug where tooltips in Team Planning and Roadmap Boards were not being displayed in their intended location, but instead showing up at the top left corner of the screen.

...

• New ‘Team Iteration Overview’ Report Widget: Reports for projects at the Team level now feature a new widget that provides an overview of all planned issues for each of the Iterations of the selected PI. The ‘Team Iteration Overview' widget showcases issue count, estimated capacity, planned load, and burned Story Points per Iteration. This feature simplifies the process of monitoring progress on individual team issues and promptly identifying any obstacles that arise.

Bugfixes

• ART Planning Board not displaying PI Iterations: Fixed a bug that occasionally prevented the ART Planning Board from displaying iterations of a PI when the ART was part of a Large Solution Train.

April 5, 2024

Bugfixes

• Issue with correctly assigning Agile Hive Administrator groups after app installation: Fixed a bug that caused random user groups to be displayed as holding the Agile Hive Administrator permission after installing the app from Atlassian Marketplace. This issue was purely visual and has been resolved.

• Primary Scrum board detection not working as intended: Fixed a bug related to the automatic detection of a Jira project’s primary Scrum board for use with Agile Hive for Team-level projects. This bug caused iterations of PIs to not be accurately mapped to their corresponding Jira Sprints in the primary board, rendering Team Planning Boards unusable.

• Report widget ‘Business Value Delivered’ stopped working for Team level projects: Fixed a bug that caused the Report widget 'Business Value Delivered' to stop displaying data for Team-level projects.

...

• ‘Expand / Collapse All’ toggle in Team Planning Boards: Team Boards now feature a new toggle switch that enables expanding / collapsing of all currently visible Feature swimlanes on the board. This option is especially useful when you need to concentrate on specific Features and eliminate any surrounding distractions.

Bugfixes

• Some Report widgets stuck in loading state when refreshing: Fixed a bug that caused certain widgets in Reports to become stuck in a loading state when refreshing data.

• Modal does not reset on Cancel when creating new PIs: Fixed a bug that caused the modal dialogue to retain old data for date input fields when the user canceled the process of creating a new PI and started over.

...

• New ‘ART PI Objectives’ Report Widget: Reports for projects at the ART level now feature a new widget that provides an overview of all ART Objectives for the selected PI, along with a comprehensive view of the Business Value Delivered by all Teams operating within the ART. Moreover, the widget computes the ART Business Value Delivered based on the average across all Teams. For more detailed information on PI Objectives of a specific Team, simply click on the Team panel to navigate directly to the Team’s individual Reports.

• ‘Update Data’ button for Reports, Team Planning, and Roadmap Boards: As the majority of Agile Hive’s views showcase real-time data, it's possible for changes to occur (especially in the context of PI Planning) while you're viewing a particular page. To keep you informed about the currency of the data you're working with and to promptly refresh the view with the most recent information, we have included an ‘Update Data' button in the top right corner next to the 'Help' menu. This button not only indicates how long it has been since you last updated the data but also allows you to do so with a single click. One significant advantage of updating only the data instead of reloading the entire page is its lightning-fast performance - try it for yourself!

Bugfixes

• ‘ART PI Overview’ widget now displays all ART issues worked on in selected PI: Fixed a bug that caused the ART PI Overview widget to only display ART level issues planned using the ART Roadmap Board. It failed to include ART issues not in the Roadmap Plan but being worked on in the selected PI based on Stories planned at the Team level, which is contrary to its intended functionality. The widget now includes all ART issues being worked on in the selected PI.

...

• New ‘ART PI Overview’ Report Widget: Reports for projects at the ART level now contain a new widget offering comprehensive insights into all planned ART issues for the selected PI. The ‘ART PI Overview' widget showcases details on WSJF, Assignee, and Progress, along with aggregated Story Points from issues across all teams operating within the ART, across all workflow categories. Furthermore, you can delve further into tracking each team's progress in delivering their portion for every ART Feature. If a Team is behind the plan, you can investigate further by clicking on the Team's icon to directly access the relevant report.

Improvements

• Improved visualization for ‘Assigned PIs’ field in Jira Issue Create dialogue: When creating a new Objective or Risk issue, you now have a more convenient way to directly input Assigned PIs information. The input field for Agile Hive's 'Assigned PIs' Custom Field has been redesigned, offering an enhanced interface and user experience.

March 5, 2024

Improvements

• Locally calculated Risk Exposure and WSJF Value in Reports: To promptly show accurate Risk Exposure and WSJF values, Agile Hive has implemented a feature where these values are computed locally in your browser when you access a Reports page. Particularly, after generating new issues involving Risk Exposure or WSJF, the computation of these fields is only triggered once the issue has been fully displayed by at least one user in the Jira Issue View.
  This is due to a current limitation of Atlassian Forge development platform. More information can be found here: Technical Limitations. We’re closely monitoring the development of Forge platform and intend to further improve this functionality in the future.

...

• Conveniently create Objective and Risks from the Reports page: Objective and Risk widgets in the Reports page now provide a convenient way to directly add new issues of the correspondent type. Simply click the ‘+' button in top right corner of the widget panel to display Jira’s ‘Create issue’ modal that is already filled based on the project context you’re in. After creating a new issue the Report widget updates automatically without need for a full page reload.

Improvements

• Adjusted zoom factor in Solution Train Roadmap Board: To better reflect the time periods planned in the Roadmap Board of a Solution Train project we adjusted the default zoom factor for the board.

February 22, 2024

Bugfixes

• Editing risk information updates the correct Custom Fields: Fixed a bug that resulted in the wrong Custom Fields being updated after providing input in the Agile Hive Issue Context for Risk-related information.

...

• View all Milestones / Objectives / Risks in Jira Issue Navigator: We added an option to view all issues listed in an Reports widget in the Jira Issue Navigator, making it easy to retrieve further details on issues or export them. This functionality is available for Milestone, Objectives, and Risks widgets in the Reports page within Agile Hive.

Bugfixes

• List of Agile Hive Administrators not displayed in Jira Administration: Fixed a bug where the display of user groups assigned with Agile Hive Administrator permission was not functioning in Jira Administration of the app when there were over 1,000 groups on the Jira site. The limit has now been extended to 5,000 groups.Please be aware that depending on the number of user groups, it may take up to 30 seconds for the list of groups added as Agile Hive Administrators to appear.

• “Unable to find the primary board of the project”: Fixed a bug where the user was prompted with an error message when displaying a Planning Board of a project on Team level. Fixing this bug required adding new capabilities to the app’s scope resulting in this version being considered a major release (11.0.0) by Atlassian. Please refer to Upgrading and Versioning for more information on versioning of Cloud apps.

...

Improvements

• ‘WSJF Value’ field is now of type Number: To enable sorting options for issues prioritized with WSJF in Agile Hive, the 'WSJF Value' Custom Field has been updated to a Number type. For example, after conducting a JQL search for certain Features within an ART level project, you can now sort by WSJF Value in the Jira Issue Navigator. Additionally, the field will now show a maximum of two decimal digits to enhance readability.

January 2, 2024

Bugfixes

• Broken links in Agile Hive project navigation: Fixed a bug where navigation links to various project views within Agile Hive were not functioning correctly.

• Capacity resets in Team Planning Board after displaying an issue modal: Fixed a bug that resulted in the capacity of a team sprint being reset when displaying an issue through Jira's modal view.

...