semasoftware Release Notes logo
Back to Homepage Subscribe to Updates

Release Notes

See the latest features, improvements, and product updates

Labels

  • All Posts
  • Fix
  • Announcement
  • Improvement

Jump to Month

  • October 2026
  • September 2026
  • August 2026
  • July 2026
  • June 2026
  • May 2026
  • April 2026
  • March 2026
  • November 2024
  • October 2024
  • September 2024
  • August 2024
  • July 2024
  • June 2024
  • May 2024
  • April 2024
  • February 2024
  • January 2024
  • December 2023
  • November 2023
  • October 2023
Powered by

Create yours, for free!

7 months ago

Liz release note - March 2026

March 27

Azure DevOps support in Liz Chat

Liz now works with Azure DevOps repositories. Ask about commits, pull requests, and code the same way you already can with other connected repositories. Product groups display repositories from all connected providers, grouped by type.

March 26

Linear integration expansion

Executive insights and daily messages are now available for organizations using Linear — previously limited to those on Jira. Ticket quality scores can be filtered by cycle and project milestone, matching sprint-level filtering already available for Jira. Additional chat query capabilities for Linear close remaining feature gaps with the Jira experience.

March 24

Zoom Integration now supports OAuth sign-In. 

You can now connect your Zoom account to Liz in one click via OAuth Sign-In. Liz automatically syncs your meeting recordings, and categorizes calls as customer or internal, so customer evidence flows into your alignment analysis without manual uploads.

Note: Your Zoom admin may need to pre-approve Liz in the Zoom App Marketplace. Multi-user accounts typically require admin approval for new apps.

Personal messages in shared reports

When sharing a report via email, you can now include a personal note for the recipient.

AI response accuracy

Liz no longer adds sign-off names to email drafts unless you explicitly ask. File upload errors now display the actual issue instead of a generic failure message.

General improvements
• Returning to a previous chat session no longer gets stuck in a loading state.
• Ticket quality views now show a proper empty state instead of a broken layout when no data is available.
• Background analysis activates automatically after onboarding completion.
• Links to preset insights within chat responses now open the correct homepage card.
• Liz no longer offers download links that do not exist.


Security updates

Hardened the container image supply chain with cryptographic verification, preventing dependency tampering during production deployments.

Avatar of authorMatthew Thaokhamlue
7 months ago

Liz release note - March 2026

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.

Avatar of authorMatthew Thaokhamlue
8 months ago

Liz release note - March 2026

March 13

Linear reaches scoring parity

Linear tickets now have full scoring support across the platform. Quality scores, filters, charts, and chat queries all work with Linear data — including image attachments, original ticket type filtering, and the ability to ask Liz about Linear ticket scores directly in conversation.

March 11

Ticket completeness score — redesigned

The ticket completeness score experience has been fully rebuilt and is now live. The new interface includes ticket priority as a visible and filterable field, clickable metrics that link directly to filtered ticket views, charts that respect your actual ticket types, and a streamlined cycle time table showing only relevant workflow statuses.

Full meeting transcript access

Liz can now read complete meeting transcripts — not just summaries — when answering questions. This enables more accurate responses when you ask about specific discussions, decisions, or commitments from customer and team calls.

General improvements

• Chat sessions can now be opened in new tabs via right-click
• Liz no longer references documents mentioned inside uploaded files that it cannot access
• Improved chat experience on larger screens
• Organizations with multiple code repository connections now route queries correctly
• Ticket images and attachments now display correctly in detail views
• Feedback buttons restored on chat responses
• Document uploads now succeed for a wider range of content types
• Improved reliability during initial setup, including custom field configuration and scoring template defaults
• Report emails now have cleaner formatting
• Filenames in responses no longer incorrectly appear as clickable links
• Chat input no longer becomes unresponsive during heavy usage
• Improved scoring accuracy
• Improved visual consistency and connection management


Security updates

Patched critical infrastructure vulnerabilities and updated AI processing dependencies to address known security issues.

Avatar of authorMatthew Thaokhamlue
8 months ago

Liz release note - March 2026

March 5

Cycle time analytics

A new analytics table shows how many tickets are in each workflow status, their average quality scores, and how long they spend there. Individual ticket pages now include a visual cycle time breakdown — making it easy to spot where work flows smoothly and where it stalls.

First insights after setup

New users now see a curated set of initial findings immediately after completing setup. You get value from Liz before running your first conversation.

Linear scoring parity

Organizations using Linear can now assign quality scoring templates and have tickets automatically classified by type. This brings Linear to the same scoring capabilities previously available only for other project management tools.

March 4

Meeting intelligence and alignment

Liz now automatically categorizes Zoom meetings as customer-facing or internal and extracts recurring discussion themes from transcripts. A new alignment report cross-references these themes against your engineering work — showing which customer needs are addressed by active development and which have no coverage.

March 2

Liz without integrations

You can now use Liz before connecting your code or project management tools. Upload documents or complete the business context questionnaire, and Liz can answer questions and generate insights from that context alone.

General improvements

• A new dimension analysis view highlights your three strongest and three weakest quality scoring areas with 30-day trend comparisons
• Reports now use your full organizational context for improved accuracy and relevance
• Reports are now included directly in email bodies — no need to open attachments
• You can now invite team members directly when sharing a report or saving a preset
• Custom field filters now apply across charts and summary statistics, not just tables
• Ticket quality score pages now load faster, especially for larger organizations
• The ticket detail page has been redesigned with an updated layout, refined score display showing current workflow stage, and improved mobile support
• File uploads now accept a broader range of valid document formats
• Liz now includes a transparency note that responses should be verified for important decisions
• Fixed an issue where navigating away during a response could cause it to appear blank
• Fixed stability issues affecting ticket quality score views
• Fixed an issue where report emails could be sent without content


Security updates

Applied security patches to backend framework and document processing dependencies.

Avatar of authorMatthew Thaokhamlue
8 months ago

Liz release note - February 2026

February 27

Multiple Zoom accounts

Your organization can now connect multiple Zoom accounts. Each account is labeled with its display name, and transcripts sync across all connected accounts — giving Liz a more complete view of your customer and team conversations.

February 26

Ticket relationship explorer

The ticket detail view now shows the full relationship map — parent, children, and linked tickets — each with its own quality score. See at a glance how well-specified the surrounding work is, not just the ticket you're looking at.

February 25

Export conversations

You can now export any Liz conversation as a formatted document. Use the export option in the session menu to download a complete conversation for sharing or archiving.

February 23

Deeper ticket quality scoring

Ticket quality scores now incorporate comments from your project management tool as additional context, not just the description and fields. Liz also now tracks and displays the reason behind each score change — whether it came from a content update or a template adjustment.

Custom field filters

You can now filter ticket quality views by your organization's custom fields. Custom fields are fully integrated into scoring, filtering, and navigation.

General improvements

• Liz now understands ticket workflow stages, providing richer answers about where tickets are in your process
• Time-in-stage calculations now include the current status period for more accurate cycle time data
• Development activity insights now include all code changes, even those not linked to specific tickets
• Tables pasted into conversations now render with proper formatting
• Responses are now saved automatically, even if a session is interrupted
• Sprint fields are now automatically detected during configuration
• Reports now correctly identify completed work within date ranges
• Ticket score history is now displayed in chronological order
• Fixed several interaction issues with dropdowns, tab switching, and navigation across ticket views
• Fixed an issue where inviting a user who already had an account could produce an error
• Faster page loads


Security updates

Resolved high-severity vulnerabilities in frontend dependencies and hardened document processing against malformed input.

Avatar of authorMatthew Thaokhamlue
8 months ago

Liz release note - February 2026

February 19

Zoom meeting intelligence

Connect your Zoom account to bring meeting context into Liz. Once connected, Liz automatically syncs your recorded meetings and generates summaries. You can search past meetings, view summaries, and reference conversations directly in chat — no switching between tools. In-app setup guides walk you through the connection, with automatic validation to ensure your account is configured correctly before anything syncs.

February 18

Custom field support for ticket scoring

You can now map your Jira custom fields to ticket completeness scoring dimensions and fine-tune how each one is evaluated. This gives you more control over how Liz scores your tickets, so completeness reflects what actually matters to your team's workflow.

February 17

Redesigned report sharing

Sharing insights with your team is faster. The updated experience lets you send to multiple recipients at once from a cleaner interface, with the option to include yourself on the distribution.

February 16

Blocking relationships in ticket details

When viewing a ticket, you can now see which other tickets are blocking it and which tickets it blocks. This makes it easier to trace dependencies and identify what needs to unblock before work can move forward.

General improvements

• You can now subscribe to daily insight emails in addition to weekly
• View ticket completeness scores for Jira projects not assigned to a product group under a new "Ungrouped Projects" filter
• "Last 24 hours" is now available as a time range when chatting with Liz
• Liz now tracks how long tickets spend in each workflow stage, so you can ask where work gets stuck
• More complete results when asking Liz to search your Jira data
• Fixed missing action buttons in chat (save, share, download, and feedback)
• Fixed an issue preventing edits to active scoring templates
• Liz no longer incorrectly blocks legitimate team-level questions about your organization
• Ticket completeness scores now display accurately when filtering by status
• Fixed links to Linear issues in chat responses
• Resolved a loading delay when switching between chat sessions
• Fixed document processing failures for certain uploaded files
• Clearer error messages when uploading unsupported file formats
• Smoother onboarding setup flow
• Fixed errors that could occur when querying certain Jira custom fields

Avatar of authorMatthew Thaokhamlue
8 months ago

Liz release note - February 2026

February 13

Linear integration

Liz now connects to Linear. Link your Linear workspace in settings and ask Liz about your Linear projects, issues, and cycles alongside your existing code and project management data.

Intelligent custom field support

Liz now automatically discovers your custom fields, evaluates which ones matter for ticket quality, and incorporates them into scoring and search results. A new settings page lets you review and adjust how each field is used — no manual mapping required.

Expanded document uploads

You can now upload documents in additional formats — including PDF, Word, Excel, and PowerPoint. Liz extracts the content and makes it available in conversations and analysis.

Shareable dashboard views

You can now share your exact ticket completeness view — including all filters, sorting, and chart settings — with a single URL. Navigation state is fully preserved when the recipient opens the link.

February 12

Real workflow statuses

Ticket completeness scores now show your actual workflow statuses instead of generic stage labels. Filter and chart by the statuses your team uses day-to-day.

February 10

Ticket detail page

Each ticket now has a dedicated detail page with a two-panel layout: description and fields on the left, quality score with a visual chart and dimension-by-dimension analysis on the right. Open it from any row in the ticket table.

General improvements

  • Liz now has access to your team structure and uploaded documents, providing more contextually relevant responses
  • Liz can now answer questions about how tickets changed over time — such as when a status changed or priority shifted
  • Liz now provides team-level analysis when questions involve individual contributors, keeping insights useful while protecting privacy
  • You can now edit scoring templates that are currently active
  • Redesigned report delivery history with date-grouped entries and easier navigation
  • Renaming conversations now works correctly
  • Improved chat stability — fixed issues with disappearing messages, streaming interruptions, and progress indicators
  • Improved reliability during initial setup
  • Fixed a display issue with score indicators in the ticket table

Security updates

Addressed infrastructure vulnerabilities and updated platform dependencies.

Avatar of authorMatthew Thaokhamlue
8 months ago

Liz release note - February 2026

February 6

Flexible report scheduling

You can now schedule reports on a weekly or monthly basis and choose which days to receive them. Liz can also generate reusable report templates from your conversations, so you can save and repeat insights without manual setup.

Redesigned onboarding experience

Setting up Liz is now clearer and faster. Connection setup is split into dedicated pages for your code repository and project management tools, with a new progress tracker so you always know where you are. Analysis begins when you're ready.

February 4

Epic and initiative filtering

You can now scope Liz's analysis to specific epics or initiatives. This applies across chat, ticket completeness scores, and insights — letting you focus on exactly the body of work that matters to you.

February 3

Sprint-aware conversations

Liz now understands your sprint schedule. Ask about your current, previous, or upcoming sprint and get answers aligned to your actual sprint boundaries.

Redesigned ticket completeness dashboard

The ticket completeness score view has been fully redesigned with a sortable, searchable table, pagination, dimension-level filtering, and color-coded quality indicators — making it faster to scan and prioritize tickets that need attention.

General improvements

  • Liz now tells you when a query analyzed a subset of results and offers to adjust scope
  • Liz now includes richer ticket detail in responses, including full descriptions and change history
  • Your timezone is now automatically detected — time-based questions respect your local time
  • Emails from Liz now render with proper formatting
  • Copying responses to email now preserves tables, lists, and structure
  • Conversation titles are now cleaner and more descriptive
  • Conversation history now supports pagination for navigating past sessions
  • Improved accuracy when interpreting ticket statuses across different project configurations
  • Fixed an issue where some responses could appear incomplete
  • Fixed duplicate messages occasionally appearing in conversations
  • Fixed a display issue affecting certain ticket views
  • Improved error handling when connection credentials need to be refreshed
Avatar of authorMatthew Thaokhamlue
a year ago

AI Code Monitor Beta V3.14: ROI of Cost of AI Tools - at Repo groups, Rolled-up ROI number at Organization level

Here's the latest video release notes -- https://youtu.be/8ojwiXXV68E

In the current release, we have implemented ROI of Cost of AI Tools - at Repo groups, Rolled-up ROI number at Organization level

1) V1.3 ROI Calculation: ROI of Cost of AI Tools

Measuring ROI of Cost of AI tools happens at the repository group / product level and at Organization level. The Technical lead or CTO of an organization can look at the 'Total Impact' to view this information along with the in the saved time (hours) and cost ($) that has happened as a result of GenAI usage in the various repository groups. 

Depending upon the Cost of AI tools per developer, number of developers in each Repository group, and the Cost saved, the Technical leads can see the impact in terms of ROI of cost of AI tools. To view this calculation, you will have to set 'Per Developer Monthly cost of GenAI tools' in the Settings page. 

Capture the field in Settings >Organization level:

Display ROI of Cost of GenAI Tools at Repo Group1:


Display ROI of Cost of GenAI Tools at Repo Group2:

Display ROI of Cost of GenAI Tools at Repo Group3:

Display ROI of Cost of GenAI Tools at Organization level:


Avatar of authorMatt Van Itallie
2 years ago

AI Code Monitor Beta V3.13: ROI of AI - Time and Cost saved at Repo groups, Rolled-up ROI numbers at Organization level

Here's the latest video release notes: https://youtu.be/Tzj1_9ZX41E

In the current release, we have implemented a few customer-centric features, which are explained below:

1) V1.1 ROI Calculation: Saved Time & Cost

Measuring ROI of AI happens at the repository group / product level. The Technical lead or CTO of an organization can look at the 'Total Impact' in the saved time (hours) and cost ($) that has happened as a result of GenAI usage in the various repository groups. Depending upon the productivity achievement and number of developers in each Repository group, the Technical leads can see the impact in terms of cost & time saved. To view this calculation, you will have to set 'Number of Developers' and the 'Average developer yearly cost ($)' in the Settings page. At the moment, we are assuming 1500 working hours as the number of yearly hours worked by a Developer.

Demonstration: In this example, for sample product "Front End Code": The Productivity Achievement is 12%

The results are:

1. Time saved annually are 3600 hours

2. Cost saved annually are $12,000


2) V1.2 ROI of AI (Rolled-up stats on Home page)

  • The CTO and other senior executives can view the rolled-up number for the 3 stats: 

    • Productivity Achievement%
    • Potential Productivity Captured%
    • Total Impact (Time and Cost savings)
  • This displays the weighted average of the Productivity achievement% and weighted average of Potential Productivity Captured% across all repository groups of this organization, while the Total Impact is total of the Hours saved and Cost saved across all repository groups of this organization

Demonstration: In this example, for sample product "Front End Code" and "Testing repos group2": The Productivity Achievement% are available for the different Repo Groups ; the Potential Productivity Captured% are available for the different Repo Groups, and the Time saved & Cost saved are available for the different Repo Groups 

The results are:

1) Organization-level Productivity Achievement% is 9%

2) Organization-level Potential Productivity Captured% is 67%

3) Organization-level Total Impact (Time and Cost savings) are 5117 hours and $17,058


Avatar of authorMatt Van Itallie