March 20

Share and download preset insights

Homepage insights can now be shared via email or downloaded as PDF and Markdown files. A feedback button on every insight page lets you share what is working and what is not.

March 19

Linear ticket analysis

The keystroke command (e.g. /qual, /why, and /size) commands now work on Linear tickets, bringing the same quality, purpose, and sizing analysis previously available only for Jira. Linear cycle data is also available for query in Liz chat.

Refresh insights on demand

A refresh button on preset insight detail pages regenerates results immediately instead of waiting for the next scheduled run.

March 18

Clickable ticket references

Ticket references in Liz chat, shared reports, and insights now link directly to both the source ticket and its Ticket Completeness Score page.

March 17

Dependency and blocking analysis

Liz can now analyze blocking relationships and cross-project dependencies in Jira. Ask what is blocking a ticket, what a team is blocked by, or find all dependencies across projects.

Cycle time by workflow stage

A new view on the Ticket Completeness Score page groups scores and cycle time by workflow stage — To Do, In Progress, and Done — with 30-day trend comparisons.

March 16

Alignment score correction

The Overall Alignment Score now uses a corrected calculation.

General improvements

• Chat drafts are preserved when switching between conversations.
• The response indicator stays active until Liz finishes generating an answer.
• Follow-up messages stay in the same conversation instead of creating a new one.
• Conversations started from homepage insights now appear in the chat sidebar.
• Documents can be uploaded directly from the Alignment Score sidebar.
• A search bar on the homepage lets you filter and find specific nodes.
• Onboarding shows a progress bar during initial insight generation.
• Duplicate notifications are suppressed.
• The Ticket Completeness Score page shows a meaningful empty state when no data is available.
• Score markers no longer appear on ticket references when no score exists.
• Jira boards without sprint support no longer produce errors.

Security updates

Applied dependency updates across backend and frontend packages. Updated vulnerability scanning configurations to reflect current risk assessments.