From Figma publish to GitLab ticket in seconds

Watcher in your GitLab flow

Watcher observes each Figma library publish and captures what changed on components, variants, styles, and tokens.

Lyse turns that signal into clear, scoped work so design and delivery stay aligned without rewriting specs or chasing screenshots.

Figma publish becomes a GitLab ticket

Lyse integrates with GitLab so each relevant design system update lands as a clean ticket in the project you choose.

On publish, Watcher creates a concise summary of the change with acceptance hints and design specs (variables, properties, variants…), giving engineers the context to start immediately and keeping the tracker close to reality.

Ticket to merge request with Lyse

Pair Lyse with GitLab to close the loop. A change happens in Figma, Watcher opens a scoped ticket, and Gitlab helps move it forward by drafting merge request content or assisting agent workflows.

This fits routine work like style tweaks, layout adjustments, edits to existing components and variants, and safe removals. Engineers keep review and merge control.

Benefits your team feels

• Tickets arrive on publish so no one rebuilds context from memory

• Ownership stays clear when updates land in the right GitLab project

• Duo receives structured context to turn tickets into draft MRs safely

• A traceable path from Figma change to ticket to MR reduces rework and speeds reviews

Questions teams ask

How does this reduce cycle time ?

Each publish becomes a ready GitLab ticket with a change summary and acceptance hints. Fewer pings and meetings and faster MRs.

What updates fit best for Duo ?

Style and layout tweaks inside existing components and variants and clean removals. Net new components still benefit from human pairing.

Can we target specific projects or code owners ?

Yes. Route tickets to the right GitLab project and label ownership so the correct team picks them up.

Does this replace PMs or Design System Managers ?

No. Lyse removes mechanical handoff work so leaders focus on priorities and reviews while protected reviews and merge requests keep final control with engineers.

What this means for delivery ?

If your source of truth is in Figma and your code lives in GitLab then Watcher closes the gap.

Design changes arrive as actionable tickets with the context GitLab Duo and engineers need to ship safe updates and keep your design system in sync with production.

Try Lyse for free

If your team ships from a Design System, Watcher is the fastest way to keep design, tickets and code in lockstep.

Request early access and watch your next Figma publish turn into clean, ready-to-run tickets in the tools your team already lives in.