Guide
Fibery reports allow you to create simple or complex visualizations from Fibery data.
Report visualisation types
There are 4 types of visualizations within a report: Chart, Table, Metric (KPI) and Pie chart.
Every report will contain one or more views, and each view can be of any one of these four visualization types.
How to create a report
Click + next to the Space name
Select View and then Report
Select a visualization type (Chart, Table, Metric (KPI) or Pie Chart) for the first view, or choose from a predefined template
Choose the data source options (see below) and click Create
Data source options
The following options are available during configuration:
Data source
Choose Current data or Historical data. See Current vs Historical data in Reports for the distinction.
Databases
Choose one or more databases from within your workspace - these define the basic data set to be used.
Note: there are no Lookups possibilities in reports.
Reports cannot automatically pull data from related records. This means that, for example, when you're building a report on the Bug level, you won’t be able to see the Sprint status unless that information exists directly on the Bug entity.
If you need data from a parent or related entity, you first need to create a Lookup field in the source database. This Lookup will copy the relevant information (e.g. Sprint status) to the Bug level, so it becomes available for reporting.
Filtering the source data
Limit the entities that will form the data set by applying filters to the databases. You can toggle context filters if the report is a context view.
Additionally, filters can be defined when configuring the report (in the Report editor) and when viewing the report. See Report filters.
Cache
When you view a report, you will be shown the last time the report was updated (to reflect changes in the source data set). The report is 'cached' (= not refreshed) unless a minimum period of time has elapsed since the last update. This is the cache setting.
You can always manually force an update on any report view by clicking the last updated message in the top right of the report:
You can also see/change the cache setting by clicking on the clock:
Once you have chosen the source options, you will be taken to the report configuration page (a.k.a. the Report editor).
Sharing
You can make a report available to people outside of your workspace by sharing the report.
Click Share in the options menu for the report (top right corner) and you will be taken to the sharing options.
The upper URL can be directly pasted into a browser address bar, allowing anyone to see the report.
The lower URL can be used to embed the report anywhere iframe is supported.
Exporting and printing
A visualization view in a report can be exported from the options menu in a number of formats: JSON, CSV or PNG.
The first two options will generate text records of the presented data, the PNG option will generate an image of the selected view.
The Print option will allow the current visualization view to be printed.
Next: Report editor
FAQ
My clients can’t access shared reports and are seeing a block message. What can I do?
If you are receiving a message that blocks access to shared reports, it’s likely due to your organization’s security settings - particularly if you use Microsoft Defender for Office 365.
Unfortunately, there’s no URL we can provide to request unblocking from our end. The resolution will need to happen on your side.
Here you can whitelist the necessary URLs:
Allow or block URLs with Microsoft Defender for Office 365
Can I set a fixed range for graph axes (e.g. always show 0 – 5 for scores), regardless of the actual data values?
At the moment, reports automatically take axis values from the data. There isn’t a built-in way to manually lock the axis range for numerical values.
For timelines, you can use the TIMELINE() function to define a range, but this approach has some limitations:
It doesn’t work well when start and end dates are the same (you need to add a minimum width).
It doesn’t work reliably with dynamic ranges (e.g. ADD_MONTH(NOW())).
Even with static ranges, results can sometimes be inconsistent.
For numerical axes (like scores from 0 to 5), currently the only workaround is to add annotations to visually indicate (and thus force) the desired range.
Why isn’t my report sorting correctly when I use a reference field (e.g. Quarter)?
Reports can only sort by aggregated data, not by individual field values. Each X-axis label in a report represents a group of records, so sorting needs to use an aggregation function like AVG(), FIRST(), or LAST() rather than a plain field reference.
Why can’t I just use the reference field (like Quarter → Quarter Sequence) directly in the report?
Reports don’t support nested fields (e.g., Quarter.QuarterSequence). You can only use fields that belong directly to the selected database.
As a workaround, you can create a Lookup field in your main database (e.g., Initiative) to bring in the needed value (like Quarter Sequence). Then, use an aggregation such as AVG([Quarter Sequence]) in the report for sorting.
Why does using AVG() work, but not ABS() or similar functions?
Sorting in reports happens after the data is aggregated. When you group by a field (like Quarter), the report only sees one row per group — so you can sort by aggregated values like AVG(), FIRST(), or LAST(), but not by non-aggregated or unrelated expressions like ABS().
Can I use functions other than AVG() for sorting?
Yes. FIRST() or LAST() can often make more sense and are easier to understand — especially if the grouped data always contains identical values for the sorting field.
Why is Sort behavior different from boards or other views?
Boards fetch and sort entities individually, while reports aggregate data by group (e.g., category, quarter, etc.). That’s why reports require aggregation functions for sorting — they don’t work directly with individual entities.