Ops & Chief of Staff · Track & Escalate
Every design marked "Ready for Dev" gets a matching Jira ticket
Doe scans Figma weekly, creates Jira tickets for unlinked designs, updates links when specs drift, and escalates handoffs stuck without sprint assignment for 7+ days.
Works acrossFigmaJira
What you get.
Every Figma design marked "Ready for Dev" cross-referenced against Jira tickets weekly. Missing tickets created, stale Figma links updated, and handoffs waiting 7+ days for sprint assignment flagged automatically.
Designs get lost between Figma and the backlog
A designer finishes a spec and updates the Figma status. Nobody creates the Jira ticket. Or they create it but link the wrong Figma file. Or the design changes after the ticket is created and the dev builds from an outdated version.
A designer spent 3 weeks on a checkout redesign. She marked it "Ready for Dev" in Figma on January 8. The Jira ticket was created January 22, a 14-day gap. By then, the designer had iterated on the spec twice. The dev built version 1. QA flagged the mismatch. Two weeks of dev time wasted because the handoff was stale.
What changes.
- 01Handoff gapBefore · Days or weeks between "Ready for Dev" and Jira ticket creationWith Doe · Missing tickets created within 24 hours of the Monday scan
- 02Spec driftBefore · Dev builds from an outdated Figma versionWith Doe · Jira links updated automatically when the Figma file changes
- 03VisibilityBefore · Nobody knows which designs are waiting for devWith Doe · Live tracker with status for every "Ready for Dev" design
- 04Stale handoffsBefore · Discovered when someone asks "what happened to that design?"With Doe · Flagged automatically after 7 days without sprint assignment
How Doe tracks design-to-dev handoffs
- 01Scans Figma for all designs marked "Ready for Dev"Figma12 designs currently marked "Ready for Dev" across 3 projects. 4 have been in that status for over 7 days. 2 Figma files were updated after their linked Jira ticket was created (spec drift). 1 design has no linked Jira ticket at all.
- 02Cross-references Figma links in Jira ticket descriptionsJira8 of 12 designs have matching tickets. 3 tickets link to outdated Figma versions (the file was updated but the Jira link still points to the old version). 1 ticket references a Figma file that was moved to a different project.
- 03Creates missing tickets, updates stale links, and flags gapsDoe1 missing Jira ticket created (checkout flow v3, assigned to frontend backlog). 3 tickets updated with current Figma version links. 4 stale handoffs (7+ days with no sprint assignment) flagged to the engineering manager. Tracker: 8 on track, 3 updated, 1 created, 4 stale.
- 04RecurringEvery MondayWeekly scan keeps the Figma-to-Jira pipeline clean: missing tickets created, stale links updated, stuck handoffs escalated. Handoff tracker maintained in Doe, missing tickets created in Jira.
Up and running in under ten minutes.
- 01Connect your toolsOne-click OAuth for each integration. No API keys, no engineering.
- 02Describe what you need“Every Monday, scan Figma for all designs marked "Ready for Dev," cross-reference each one against Jira tickets, create tickets for any unlinked designs, update Jira links where the Figma file has changed, and flag any handoff that has been waiting 7+ days without a sprint assignment.”
- 03It runs on scheduleRuns every Monday morning. Handoff tracker updated in Doe, missing tickets created in Jira.
Before you delegate.
- 01Does it work with Linear instead of Jira?Yes. Doe supports Jira, Linear, and Asana as the engineering task destination. The Figma scanning works the same regardless of which project management tool you use.
- 02How does Doe detect spec drift?Doe compares the Figma file's last-modified timestamp against the Jira ticket's creation date and the linked version. If the Figma file was updated after the ticket was created, it flags the ticket and updates the link.
- 03Can it handle multiple design teams?Yes. Doe scans across all Figma projects you connect. Each team can have its own naming conventions and status labels. You configure which Figma status means "ready for handoff" per project.
- 04What if the designer intentionally updated Figma without it being a spec change?Doe flags the change but does not auto-modify the Jira ticket. The engineering manager reviews the flag and decides whether the update is material. Minor Figma edits (like color tweaks or annotation changes) can be filtered out by configuring a change threshold.
- 05Does it assign the Jira ticket to a specific developer?By default, Doe assigns new tickets to the team backlog, not a specific person. You can configure routing rules (for example, checkout designs go to the frontend team) but individual assignment stays with the engineering lead.