> For the complete documentation index, see [llms.txt](https://docs.luciq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.luciq.ai/changelog/readme/2026-02.md). # February 2026 3 product updates shipped in February 2026. See [Product Updates](/changelog/readme.md) for the latest. {% updates format="full" %} {% update date="2026-02-26" %} ## Time Zone Support in Crash Charts #### What's new? * Crash charts across the Crashes list, Crash details, and App Health pages now correctly reflect your selected time zone. * Data aggregation and bucketing are now performed in your chosen time zone, eliminating issues with missing buckets, shifted data, and incorrect day boundaries. #### Why this matters? * Previously, chart data could appear misaligned for users in time zones behind UTC, leading to confusion when comparing data across tools. This fix ensures accurate, trustworthy, and consistent chart data regardless of your location. {% endupdate %} {% update date="2026-02-24" %} ## Metadata and Filtering in Surveys #### What's new? * Survey responses now include metadata such as User ID, Country, App Version, Device, and OS. * Each response carries its own environment context, similar to Bug Reports, Crash Reports, and Session Replays. * You can filter responses by any of these metadata fields directly on the dashboard. #### Why this matters? * Product and customer experience teams can now analyze sentiment by app version, country, device, and more. This makes it easier to detect release-specific issues or region-specific trends, and enables deeper analysis when exporting responses. #### Availability * Supported across all survey types (NPS, Customer Survey, App Rating). Available to all customers. {% endupdate %} {% update date="2026-02-24" %} ## Bug Grouping: Alerts and Rules #### What's new? * If you have Bug Grouping enabled, you can now configure alerts and rules based on report type. * Alerts can target all reports (masters, ungrouped, and duplicates) or only master and ungrouped reports to reduce noise. * Automatic tags are added to reports: "Luciq\_Master\_report" when a report becomes a master, and "Luciq\_Duplicate\_report" when marked as a duplicate. These tags can trigger rules or workflows. * The Triage Agent automatically adds a comment when a new duplicate is added to a master report. #### Why this matters? * You can avoid being overwhelmed by duplicate-triggered alerts and build smarter automation workflows based on report grouping type. Tag-based rules also improve visibility in integrations like Jira through tag and comment sync. #### Availability * Available for all customers with Bug Grouping enabled. {% endupdate %} {% endupdates %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.luciq.ai/changelog/readme/2026-02.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.