.svg){kind=logo}
Design to dev without the drama
Hand off locked designs within Jira. No need to log in to Figma.
Developers can view, inspect, and download a Figma design directly from their Jira ticket. No need for context-switching. Save your devs from having to learn the design tool or get an expensive Figma license just for design handoff.
Try Figma for Jira
Embed a locked-in version of a design so that developers are certain it’s ‘ready for dev’. Changes in Figma won’t propagate to Jira unless you update the version. This provides devs with stable requirements, minimizing rework.
Tools like Figma and Zeplin can make design handoff harder than it needs to be. Keep your stack and processes simple by encouraging designers and developers to collaborate where they’re already working, with the help of a small plugin.
Designs are pinned to your Jira issue and won’t automatically change. Devs can switch between versions to see how designs have evolved. You also have the option of disabling this feature so that the latest version is always shown.
Designs can be embedded in a collapsible list, as thumbnails, or as part of a paginated gallery. The native Figma canvas view makes it possible to embed prototypes and FigJam files (although this requires a Figma login).
Drag and zoom in on designs using the full-screen interactive viewer. Scale to the original size if you need the actual dimensions. You can also open an information panel showing additional details about the design.
A single Figma link enables devs to download designs directly from Jira in a range of formats: SVG, PNG, JPG, or PDF. This saves designers from having to upload multiple file types, and means devs can experiment, iterate, and refine faster.
Any user with access to the Jira issue is able to see the Figma file. Other Figma for Jira apps make you have a Figma account AND load a lite version of Figma within Jira. Our app allows us to cache embedded designs so they load faster.
Figma for Jira Pro works with Jira Cloud and Jira Data Center.
Figma’s free Jira app lets you embed Figma files in Jira tickets, but it’s basic and every user needs a Figma account to see the design. There’s no version control, no view options, no export options, no metadata, and no ability to scale the design to its original size.
The app is aimed at developers and designers using Jira to manage their tasks. It offers them a way to collaborate on Figma designs in Jira rather than Figma.
That said, it's also suitable for any team using Jira that needs to view Figma designs, e.g. a graphic designer sharing designs with the marketing team.
It means that when you embed a Figma file in a Jira ticket using our app, the design is pinned to the ticket. So, the current version is fixed and changes in Figma won’t reflect in Jira until a new version gets pinned.
This increases risk of rework or confusion, although it may be suitable for some workflows where design and development are very tightly integrated.
They’re different tools for different things.
Figma dev mode gives developers a detailed view of design files, but requires a Figma account. It’s not a task management tool and the ‘Ready for dev’ label doesn’t set priorities or prevent further edits.
Figma for Jira Pro links finalized designs directly to Jira tasks, so devs can quickly see the right version in context without leaving Jira.
In short, dev mode is for inspecting design details and Figma for Jira is for integrating designs into the project workflow.
Find out more in our blog about Figma dev mode and the ‘Ready for dev’ label.
Yes, you can embed public and private files. A key benefit of our app is that Jira users can access private files without logging in.
Only one user needs to have a Figma account with access to the files to be embedded. This user needs to authenticate the app to enable other users to view designs without logging in.
The two authentication method we offer are:
1. Figma personal access tokens (on Cloud and Data Center)
2. Authenticate with Figma (on Cloud only)
Our documentation offers step-by-step instructions for both Figma for Jira authentication methods.
Of course! Just ask.