Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Anchor
10.1.0
10.1.0

10.1.0

Released January 23, 2023

Report permalinks improvements

Version 9.0.0 introduced the ability for users to copy a permalink to a specific report via a link icon in the report header. This release expands on that functionality by adding a second icon that opens the report in a new browser tab.

Image Added 

A related pain point in previous versions was that opening a report in a new tab from the reports list view using standard browser controls (e.g. right-clicking on the link and selecting "Open Link in New Tab" from the contextual menu) did not work as expected, causing the user to receive an authentication error in the newly opened tab. This release includes a workaround for the underlying issue, and opening reports in a new tab from the reports list view should now work as expected.

Other changes

  • (Fix) Fixed a bug affecting users with Jira instances containing a large number of boards and filters from being able to select some of those boards and filters when configuring a report's data source.

Anchor
10.0.0
10.0.0

10.0.0

Released January 9, 2023

  • (Improvement) Upgraded various server infrastructure including migrating to a new database and database provider.

Anchor
9.3.0
9.3.0

9.3.0

Released March 1, 2022

Anchor
9.2.3
9.2.3

9.2.3

Released June 4, 2021

  • (Improvement) Additional security hardening of Atlassian Connect lifecycle endpoints.

Anchor
9.2.2
9.2.2

9.2.2

Released June 4, 2021

Anchor
9.2.1
9.2.1

9.2.1

Released November 2, 2020

...

Info
titleLimitations of "Team" field

Due to limitations of the Jira API, the team field will display the team name for shared teams only. For plan-specific teams, a generic team name will be displayed. To convert a plan-specific team to a shared team, see these instructions.

Other changes

  • (Fix) Users attempting to access a report via a shared permalink who do not have permission to access the report now receive a more helpful error message.
  • (Fix) Fixed a bug that prevented saving report changes when only the category was modified.  

...

This release introduces the ability for users to copy a permalink to a specific report, allowing the report to be accessed directly in a new browser tab, saved as a browser bookmark, etc. To copy the permalink to your clipboard, simply open the report and click the link icon next to the report name in the heading.

Other changes

  • (Improvement) Migrated the entire codebase to TypeScript.
  • (Fix) Fixed a bug that caused the app to fail to initialize for users without a valid Jira Software license (i.e. Jira Core or Jira Service Desk only).

...

More display preferences will be added in future releases. Suggestions are welcome!

Other changes

  • (Improvement) Polished up some rough edges that were left over from the recent user interface redesign. 
  • (Improvement) Performance improvements when modifying report settings while the report data loads.
  • (Change) Empty aggregation values in the grouping header now display nothing instead of "N/A".

...

  • Open: Previously called Public. Reports configured with Open access can be viewed by any logged-in user. Only designated administrators can modify or delete the report.
  • Limited: Reports configured with Limited access can be viewed only by specified users or members of specified groups. Only designated administrators can modify or delete the report.
  • Private: Reports configured with Private access can be viewed, modified and deleted only by designated administrators.

Other changes

  • (Fix) Fixed a bug that interfered with the ability of report administrators to make changes to settings while report data was loading.
  • (Fix) Fixed a bug that prevented all users from being available in user selection fields when creating filtering rules.

...

To restart the data loading process, click the Refresh report data button in the report toolbar.

Other changes

  • (Improvement) This release further refines the user interface for configuring report settings. Drag-and-drop reordering of rules has been reintroduced with a faster and more reliable implementation, form validation is more robust, and a few things have changed under the hood to allow for multiple rules based on the same field to support filtering rules and a couple of other upcoming features.
  • (Change) Formula fields have been used in production since May 2016, and have proven both reliable and useful for a variety of use cases. Additionally, the user interface improvements in this release make it easier for report administrators to configure formula fields. Therefore, the feature has officially graduated from Labs status in this release.
  • (Change) Added a custom app icon to the Jira navigation sidebar to more easily distinguish Limbr Reports from other add-ons when the sidebar is collapsed.

...

  • Two new aggregation operations are now supported: Count and Unique. Count reflects the number of rows containing non-empty values for the specified field, while Unique reflects the number of rows containing unique values for the specified field. While other operations are only available for number fields, Count and Unique are available for all field types.
  • Previously, aggregation calculations were only performed if an aggregation rule was configured by the report administrator. Now, all supported aggregations are automatically calculated at report runtime. This change enables aggregated values to be referenced in rollup expressions regardless of whether the aggregated value will be displayed in the report for viewers.
  • Display of aggregated values is now configured alongside other formatting controls in the column details section.

Other changes

  • (Change) The user interface for configuring grouping and sorting rules has been updated to match columns, paving the way for configuring additional grouping and sorting details in a future release.
  • (Improvement) Polished up presentation of aggregation data in the report: eliminated text overlap issues; ensured consistent alignment between grouping levels; various other visual tweaks.
  • (Fix) Fixed a nasty crash affecting new users creating their first report.

...

These are user-specific display preferences that are not saved as part of the report configuration, and therefore will reset each time the report is viewed. As was the case previously, grouping levels will begin in an expanded state when the report is initially viewed.

Other changes

  • (Fix) Fixed a crash caused by a report data load continuing to run in the background after the user has navigated away from the report. In-progress fetches are now aborted as soon as a user selects a different data source or navigates away from the report.
  • (Fix) The previous method of fetching data for Epic Links proved somewhat unreliable and has been replaced by a more reliable and efficient method. 
  • (Fix) Fixed a crash caused by configured grouping, sorting or aggregation rules referencing a field that no longer exists in JIRA. The invalid rules are now identified and simply skipped during processing.
  • (Change) Updated various language to match recent upstream changes to JIRA – most notably, "Report settings" is now used in favour of "Configure report".
  • (Change) The Filtering pane has been updated with temporary help text until filtering rules are made available in an upcoming release.

...

Note for Safari users: Safari does not currently expose the necessary API to allow the add-on to specify a filename for the export download - you will need to rename the downloaded file and add a .csv extension before opening the file in Excel or another CSV editor. This API is supported in Safari Technology Preview and will likely be included in a future stable release.

Other changes

  • (Improvement) Improved UI performance across the board. Add-on data and JIRA data are now prefetched during add-on initialization and are cached much more aggressively, resulting in fewer API calls to JIRA during most operations and generally a snappier user experience when navigating within the add-on.
  • (Improvement) The report header has been updated to match recent changes to JIRA's UI conventions: the Refresh and More Actions buttons are now more compact, with tooltips on hover. The Refresh button icon also animates during the refresh process and stops to indicate that the data has been successfully refreshed. 
  • (Improvement) All custom field types are now supported in Grouping and Sorting Rules.
  • (Fix) Fixed a long-standing bug that caused Sorting Rules to not work reliably when sorting by fields containing arrays (e.g. Versions, Components).
  • (Fix) Fixed a bug that required users to click the "Back to report" button a second time to return to the report view screen after discarding unsaved configuration changes. 

...

Users can now narrow down the list of available reports in the View Reports screen to more easily find the report they are looking for. The list can be filtered to display only reports for which the user is an administrator (My reports), by Category, and by Sharing scope (Public, Limited or Private). The new search field at the top of the page filters the list by matching text in the report name and description.

Other changes

  • (Improvement) The Epic Link field now displays the linked Epic's name rather than just the issue key.
  • (Fix) Fixed a bug loading reports when one or more report administrators had user IDs containing special characters.

...

Note
titleLabs feature

Formula fields are currently a Labs feature, meaning they are considered to be a work-in-progress. While the feature should be quite stable and usable, we are interested in user feedback to help further polish the experience of using formula fields in upcoming releases.

Other changes

  • (Improvement) Added a "Create a report" option to the main navigation dropdown.
  • (Improvement) Added "Back to report" and "Back to reports" buttons to the report header.
  • (Improvement) Reworked the menu for navigating between configuration panes. Using the browser's back and forward buttons to navigate between panes is now also possible.
  • (Improvement) Added help text to each configuration pane.
  • (Improvement) More descriptive error messages with additional help text and links to documentation where appropriate. 
  • (Improvement) The "Description" field is now available when creating or copying a report.
  • (Change) Renamed the main navigation item from "Limbr" to "Reports" to make finding reports more obvious to new users.
  • (Change) Renamed the "Data" configuration pane to "Filtering" to better reflect the scope of the pane.
  • (Fix) Added better validation of report configurations when saving changes to prevent reports from getting stuck in an unusable state.
  • (Security) Write access has been removed from the add-on's permission scope, meaning Limbr Reports no longer has the ability to persist data to your JIRA instance. We had not utilized our write access to date, and have decided to voluntary enforce this limitation through the Marketplace APIs simply as a precautionary measure.

...