Forge app for Jira Cloud
Design context that survives the handoff.
Embed Figma & Miro designs in Jira issues — pin the version, read the comments, and view without a seat. So the ticket and the design never drift apart.
The handoff gap
The design and the ticket drift apart the moment work starts.
A link in the description isn't context. It rots, the conversation scatters, and half the team can't even open it.
Stale designs
The mockup keeps moving after the ticket is written. Developers build against a version nobody can point to anymore.
Feedback scattered
Review comments live in the design tool, decisions live in Jira, and neither side sees the whole conversation.
Seats cost money
QA, PMs and stakeholders just need to see the design — but the built-in integrations make them buy a full seat first.
How it works
Three steps, then it just stays in sync.
Paste a link
Open any Jira issue, drop in a Figma file or Miro board URL. Design Bridge adds a live, interactive embed right in the issue.
Pin the version
Snapshot the exact version the ticket was written against. If the design changes later, everyone sees a clear banner and can re-pin in one click.
The team sees it
The pinned design renders as an image, so every teammate views it in Jira — comments alongside — without needing a design seat.
What's inside
Everything the built-in integrations left on the table.
Each feature maps to a real, repeated complaint about older design integrations.
Embed, live and tabbed
Attach a Figma file or Miro board to any issue. Get a live interactive embed plus tabbed views, all inside the issue panel.
Pin the version
Snapshot the exact design a ticket was written against. A "this design has changed since the ticket was written" banner appears when it moves — re-pin in one click.
No built-in integration does change detectionComments in the issue
Figma comments are pulled in and shown beside the design, so review feedback lives with the ticket instead of a separate tab.
Top-requested missing featureView without a design seat
The pinned design renders server-side as an image, so the whole team sees it in Jira — no Figma or Miro seat required for viewers.
Highest-voted complaint, solvedReliable, self-service repair
One-click "Reset connection", plain-language error messages that tell you exactly what to do, and no infinite spinners.
Answers the reliability complaintsFast by default
Thumbnail-first, lazy-loaded embeds keep the issue view snappy. The heavy design only loads when someone actually opens it.
Pricing
Simple, per-user, and free for small teams.
Billed through the Atlassian Marketplace on your existing invoice. Viewing is always unlimited.
- 1 connected design tool
- Up to 5 linked issues
- Unlimited seat-free viewing
- Version pinning & comments
- All design tools connected
- Unlimited linked issues
- Version pinning & change detection
- Comments in the issue
- Seat-free viewing for everyone
- Everything in Standard
- ~$1.20 / user at 500 users
- ~$0.85 / user at 1,000 users
- Priced automatically on tier
Annual billing is 10× the monthly rate — two months free. Pricing is counted on your billable Jira users, matching how Atlassian bills every other app on your instance.
Why Forge, why now
The modern, privacy-first way to connect design and Jira.
Built on Atlassian Forge
Runs on Atlassian's current app platform — not the older integration model that reaches end-of-support. Your admins get Forge's security and data-residency guarantees.
Actively maintained
A focused team ships fixes and features on a real cadence, driven directly by the reliability and workflow gaps teams keep reporting.
Privacy-first by design
No tracking of your design content, no third-party analytics on what you view. Your OAuth token is stored securely by Forge and never exposed to us.
Metadata-only storage
We store the design link, the pinned version reference and a rendered snapshot URL — never a copy of your full Figma file or Miro board.
FAQ
Questions teams ask before installing.
Does my whole team need Figma or Miro seats?
No. Only the person who connects a design tool needs a seat there. Once a design is pinned, Design Bridge renders it server-side as an image, so everyone else — developers, QA, PMs, stakeholders — views it directly in the Jira issue with no design seat at all.
Which design tools are supported?
Figma files and Miro boards in v1. Figma gets the full experience — live embed, version pinning with change detection, comments, and seat-free viewing. Miro boards embed and pin today, with deeper Miro parity on the roadmap.
Does it work with Confluence?
Not yet. v1 is focused on Jira Cloud. Confluence support is planned for v1.1 so the same pinned designs can appear in your specs and pages.
How is pricing counted?
Per billable Jira user on your instance, the same way Atlassian meters every other Marketplace app. Free covers up to 10 users; Standard is $2.50/user/month for 11–100 users; volume discounts kick in automatically above 100 users. Annual billing costs 10 months for 12.
Is my design data stored anywhere?
Only link metadata and a rendered snapshot image — never your full Figma file or Miro board. Everything lives in Atlassian Forge's Key-Value Store on Atlassian infrastructure. See the Privacy Policy for the full detail.
How do I connect Figma?
Open any issue, paste a Figma link, and click Connect. You'll approve a standard Figma OAuth consent screen once; the token is stored securely by Forge. Full walkthrough in the docs.
What happens when a design changes after the ticket is written?
The issue keeps showing the exact version you pinned, and a banner appears: "This design has changed since the ticket was written." Anyone with access can compare and re-pin to the latest version in one click — so nobody silently builds the wrong thing.
Does it support Miro?
Yes. You can embed and pin Miro boards in Jira issues today. Figma-specific extras like inline comments are being extended to Miro over upcoming releases.
Where does my data live, and is it private?
On Atlassian Forge infrastructure, inheriting Atlassian's data-residency options. We store metadata only and run no analytics on your design content. Details are in the Privacy Policy.
How do I get support?
Email support@designbridge.talonoid.com or see the Support page. Most questions are answered within one business day, and the troubleshooting guide covers the common errors.
Keep the design and the ticket together.
Install Design Bridge for Jira and give your whole team the design context they've been missing — pinned, commented, and viewable without a seat.