On-demand insights with a powerful reporting engine built directly into Jira
On-demand insights with a powerful reporting engine built directly into Jira
On-demand insights with a powerful reporting engine built directly into Jira
Insights on tap, directly within Jira
Slice, dice and display your Jira data, your way
Protect your data with our privacy-first approach
Forget the hassle of exporting to CSV, connecting external BI tools or waiting for an analyst; Limbr Reports enables your users to quickly and easily create and share polished reports without leaving the Jira experience!
Unlock critical insights from your Jira data with robust manipulations including nested grouping and sorting, advanced filtering, aggregations and formula fields; show off your results with precise formatting controls.
Unlike other Jira reporting apps, Limbr Reports was designed with a focus on privacy from the ground up: your data never touches our servers, and reports run fully within the boundaries of your Jira permissions model.
More details
Limbr Reports embeds powerful reporting capabilities directly within the Jira Cloud experience, enabling your users to easily leverage your Jira data in exciting new ways.
Feature highlights:
- Specify the source of data by project, board, saved filter or custom JQL query.
- Work with standard Jira issue fields, custom fields, related issue fields (e.g. the priority of the parent issue), select Marketplace App fields (e.g. Tempo Team & Account) and formula fields.
- Segment the data with nested grouping rules.
- Summarize the data with aggregations (e.g. sum, average, rollup).
- Sort the data with nested sorting rules.
- Narrow the data set with advanced filtering rules that plug the gaps in JQL.
- Decide which fields are displayed as columns and control the presentation of each column including width, header and data format.
- Share reports with others via granular access permissions.
- Privacy-focused: your Jira data never touches our servers, and reports respect your existing Jira permissions model.
Reviews for cloud
(7)Sign in to write a review
Hi Andrew,
Thanks for the review!
In fact, the next release (which is slated to go live by the end of this week) does include a permissions model. There are two permission scopes: Administrators and Sharing. Each report can have one or more administrators configured, and only administrators can edit and delete. Sharing rules determine which users can run the reports. You can configure each report to be private (accessible only to report administrators), public (accessible to all logged-in users) or shared with a specified set of users and/or groups. Additionally, reports do currently respect JIRA's issue-level permission schemes - this means that even if a user can access a given report, only those issues that the user otherwise has permission to view will be displayed in the report content.
Hope this helps. Please do feel free to raise a support request with any additional feedback, feature requests, etc.
Reviews for server
(7)Sign in to write a reviewHi Andrew,
Thanks for the review!
In fact, the next release (which is slated to go live by the end of this week) does include a permissions model. There are two permission scopes: Administrators and Sharing. Each report can have one or more administrators configured, and only administrators can edit and delete. Sharing rules determine which users can run the reports. You can configure each report to be private (accessible only to report administrators), public (accessible to all logged-in users) or shared with a specified set of users and/or groups. Additionally, reports do currently respect JIRA's issue-level permission schemes - this means that even if a user can access a given report, only those issues that the user otherwise has permission to view will be displayed in the report content.
Hope this helps. Please do feel free to raise a support request with any additional feedback, feature requests, etc.
Reviews for Data Center
(7)Sign in to write a reviewHi Andrew,
Thanks for the review!
In fact, the next release (which is slated to go live by the end of this week) does include a permissions model. There are two permission scopes: Administrators and Sharing. Each report can have one or more administrators configured, and only administrators can edit and delete. Sharing rules determine which users can run the reports. You can configure each report to be private (accessible only to report administrators), public (accessible to all logged-in users) or shared with a specified set of users and/or groups. Additionally, reports do currently respect JIRA's issue-level permission schemes - this means that even if a user can access a given report, only those issues that the user otherwise has permission to view will be displayed in the report content.
Hope this helps. Please do feel free to raise a support request with any additional feedback, feature requests, etc.
Cloud Pricing
Server Pricing
Data Center Pricing
Pricing FAQ
- How does cloud app pricing work?
Cloud apps are sold as a monthly or annual subscription. You are eligible for support and automatic version updates as long as your subscription is active.
When your subscription renews each month, you are automatically billed for apps based on the number of users in your instance.
If app pricing changes after your initial purchase, there's a 60-day grandfathering period during which you can renew based on the old pricing.
- How do I determine my cloud pricing?
Apps are billed based on the number of users in your Atlassian product. Jira Cloud apps are priced based on the maximum users of the Jira products on your instance. For example, if you have Jira Software (50 users) and Jira Service Desk (10 agents) on the same instance, you pay the 50-user price for apps.Note: While this app has features specific to Jira Service Desk, the app is technically available across the whole Jira instance. Therefore the above guidelines for licensing across maximum users still apply.
The pricing structure for cloud apps is as follows:
- Monthly subscriptions with up to 10 Atlassian product users are billed at a flat rate price.
- Monthly subscriptions with more than 10 users are billed per user, starting at the first user.
- Monthly subscriptions with more than 100 users are billed per user. The table above provides example pricing at various user levels.
If you've opted for annual billing for your Atlassian product, apps are also billed annually at a discount (12 months for the price of 10).
- Do you offer academic, community, or open-source licenses for cloud apps?
Academic, community and open source licenses are not available for cloud apps.
- Can I extend my free trial?
For cloud apps, you cannot extend your free evaluation period. All cloud apps are immediately subscribed by a user, and we provide a free evaluation period. This is a minimum of 30 days and ends on the second billing cycle after you first subscribe to the app.
Limbr Labs provides support for this app.
Vendor support resources
Find out how this app works.
Atlassian-hosted discussions connect you to other customers who use this app.
Versions
Jira Cloud • Released 2019-04-01
Summary
New descriptor URL
Installation
- Log into your Jira instance as an admin.
- Click the admin dropdown and choose Add-ons. The Find new apps or Find new add-ons screen loads.
- Locate Limbr Reports for Jira Cloud.
- Click Free trial to download and install your app.
- You're all set! Click Close in the Installed and ready to go dialog.
Similar apps
