For the complete documentation index, see llms.txt. This page is also available as Markdown.

February 2026

Luciq product updates from February 2026, a shorter month covering dashboard refinements and monitoring changes across the platform.

3 product updates shipped in February 2026. See Product Updates for the latest.

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.

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.

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.

Last updated