Creating a Historical Report to Track State Changes

Guide

This report allows you to analyze historical data in Fibery to pinpoint exactly which Entities were moved into the specific state within a desired period

For example we will use Features database and we will find out, how many of them were moved to Ready for dev state during November 2025.

It will be really helpful in advance to check out Current vs Historical data in Reports

1. Creating the Report

Create New Report.
Source: Choose the option to create the report from Fibery.
Choose Table as a Report view
1. in the end of the guide you may read why this makes sense
Naming & Database:
- Chart Name: Provide a descriptive name, such as "Features Moved to Ready for Dev."
- Database: Select the entity you are tracking, e.g., Features.
Set the Date Range
1. The Date Range in a historical report serves to limit the inclusion of modification events based on their period of validity, effectively defining the analysis window. An event is included if the time it was valid (between its Modification Date and Modification Valid To) overlaps with the set Date Range, meaning it is not strictly filtered just by the initial Modification Date.
Apply Filters to improve performance (optional)

These filters apply to the current state of the data in your database. Their primary purpose is to improve the report's performance by reducing the initial set of data the system has to scan historically.

In the first Filters section, apply high-level filters to exclude irrelevant entities.
- When applying filters in the initial "Source Filters" section, remember that these filters apply to the current state of the entity, not its historical state. For example, if you filter out features currently in the "Icebox," you will exclude all historical data for any feature that happens to be in the "Icebox" right now. If a feature moved to "Ready for Dev" in the past but was subsequently moved back to "Icebox," its entire history (including the transition to "Ready for Dev") will be excluded from the report. Use these source filters carefully, primarily for performance by excluding databases or categories of items that are permanently irrelevant, and avoid filtering on dynamic fields like State unless you intend to exclude the full history of items currently in that state.
- The key is to apply a few simple constraints to speed up the loading process.

2. Apply Filters for Historical Changes

These are the crucial filters that determine what historical event you are tracking. They are applied to the historical data, not the current data.

Filter Name	Condition & explanation
Track State Field Changes	`Change Fields contains State` This tells the report to only look at historical modifications where the State field was part of the change. `contains` vs. `contains only`: If multiple fields (e.g., State and Assigned User) were updated very quickly (within a few seconds), Fibery groups them as a single historical action. Using `contains` ensures this action is included if any part of it was a State change.
Define Change Period	`Modification Date is in November` (or your specific period) This filter refines the timeline of the changes themselves, ensuring the state transition happened within this specific window.
Target specific State Change	`Changed State is in Ready for Dev` This is the final and most specific filter. It ensures that the tracked change resulted in the feature's state becoming "Ready for Dev".

3. Visualize the Data in a Table

For maximum clarity and detail - specifically to see the exact date of the change - it is best to use the Table visualization.

In the report view, use the visualization type - Table.
Add the following columns for granular tracking:
- Name: The title of the Feature that changed.
- Date: This is the most important column, showing the exact date/time the state change occurred.
- State: (Optional) Include this initially to double-check that the resulting state is indeed "Ready for Dev," confirming your filters are correct.

Your table will provide a clean, auditable list of every Feature that hit the "Ready for Dev" state during your defined historical period, along with the precise timestamp of that transition.