A Step-by-Step Guide to Setting Up the Figma for Jira App
Struggling to connect Figma and Jira? Set up the figma for jira app, link designs to issues, and check access. Read now to get started.
Connecting Figma and Jira can make design work easier to review beside the issues it affects. But setup can feel confusing when app permissions, sharing settings, and Jira access all play a part.
A link that opens for you might still leave teammates staring at an access request. And if the design is hard to find in an issue, developers may work from outdated details.
Here’s the truth: you can set up the Figma for Jira app in a few practical steps. I’ll walk you through installation, linking designs to Jira issues, checking access, and fixing common snags.
How to Set Up the Figma for Jira App
To set up the Figma for Jira app, install or enable the integration for your Jira site, grant the required permissions, and add a Figma link to a Jira issue. Then check that the design opens for the people who need it.
Use these steps as a general path. The app’s exact name, controls, and availability can vary by Jira deployment and app version.
- Check your Jira setup. Confirm whether your team uses Jira Cloud or a self-managed Jira deployment. Ask a Jira administrator to verify that the relevant app supports your environment.
- Confirm access and permissions. Make sure you can manage apps or ask an administrator to handle installation. Check that your Figma account can open the design you plan to share.
- Install or enable the app. In Jira’s app management area, search for the Figma integration your team intends to use. Review its description and permissions, then follow the installation prompts.
- Authorize the connection if prompted. Sign in to Figma through the app’s authorization flow, then approve the requested access if it matches your organization’s policy. An administrator may need to approve the connection.
- Copy the Figma design link. Open the relevant design or prototype in Figma. Copy its share link, and check that the link’s access settings allow the intended Jira collaborators to view it.
- Add the link to a Jira issue. Open the issue connected to the design work. Paste the Figma link into the issue description or a comment, or use the app’s available linking control.
- Check the result with a teammate. Confirm that Jira displays the link or preview as expected. Ask someone with the right project and Figma permissions to open it before relying on it for review.
For example, if a checkout redesign relates to Jira issue “PAY-214,” add the Figma prototype link to that issue. A developer can then find the design alongside the work item.

What the Figma and Jira Connection Helps You Do
The integration brings design references closer to the Jira work they support. Depending on the app version and your setup, a Figma link may appear as a preview or an interactive embed.
That context can help a designer, developer, and product manager discuss the same screen while reviewing an issue. Instead of searching through chat for a prototype, a teammate can open the related Jira issue first.
But here’s the truth: adding a link does not automatically give everyone permission to view the design. Jira access and Figma sharing access are separate checks.
Check These Requirements Before Installation
A quick check before installation can save time later. Confirm who can install Jira apps, which Figma sharing rules apply, and whether the integration supports your Jira environment.
Confirm Jira administrator access
Some teams allow project administrators to manage apps. Others reserve app installation for Jira site administrators. If you cannot see an installation option, ask your administrator to confirm the policy.
Check Figma sharing settings
Choose sharing permissions that fit your team’s rules. For a private design, collaborators may need to be invited directly or belong to an approved workspace.
For instance, an external contractor might have access to a Jira project but no access to the Figma workspace. The Jira link can appear correctly while the design remains unavailable to that person.
Verify deployment compatibility
App support can differ across Jira Cloud and self-managed deployments. Check compatibility before installing, especially if your organization uses a restricted network or customized Jira environment.
Link Designs to Issues People Can Find
After installation, decide where design links belong. A consistent pattern makes reviews easier and reduces the chance that an important prototype gets buried in a long comment thread.
Choose a predictable place
For a design central to completing an issue, add the link near the top of the description or in a clearly labeled design field. Use a comment when the link is temporary or added during a discussion.
For example, a team might use a “Design” field for the current prototype and comments for review updates. That simple convention helps a new team member find the latest reference.
Use the link that matches the task
Link to the relevant Figma design, frame, or prototype when you can. A link that opens close to the screen under review is more useful than one that lands on an unrelated page.
Before sharing, open the link yourself in a separate browser session or ask a teammate to test it. This can reveal permission issues that your own account does not show.
Test the Setup Before Making It Routine
Try the connection with one Jira issue before asking the whole team to rely on it. A small test reveals whether the app displays links properly and whether collaborators can open them.
Run a short access test
Choose a low-risk issue and add a Figma link. Ask a teammate who has the expected Jira role to open the issue, follow the link, and confirm they can see the intended design.
Agree on a lightweight team convention
Decide where links go, who updates them, and how the team identifies the current design. For example, a designer can update the issue’s design field when a prototype changes, while comments record review decisions.
Here’s why this matters: the integration can make a link easier to find, but your team still needs a habit for keeping it useful. A brief convention often prevents old links from lingering unnoticed.
A Broader Project Coordination Option: ONES.com
ONES.com brings project management and knowledge management together in one platform powered by ONES Assistant. ONES Project is a Jira alternative, while ONES Wiki is a Confluence alternative; they are sold separately.

For teams managing design work across issues, decisions, and internal guidance, ONES.com offers another way to organize project coordination. It does not replace Figma or automatically provide a Figma embed; check your team’s integration needs before choosing a setup.
Value proposition
ONES.com can help teams coordinate project work and related knowledge without relying on a growing stack of separate extensions. It offers cloud and self-hosted deployments, including on-premise and air-gapped options.
Core capabilities
- Issue workflows become difficult to adapt. ONES Project supports custom workflows, so teams can shape issue movement around their review and delivery stages.
- Teams need fields that match their work. Custom fields let teams capture details such as design status or review owner, making issue context easier to scan.
- Sprint planning needs a connected process. Sprint management helps teams organize work into iterations and track planned tasks with their related issues.
- Progress is hard to interpret across work items. Built-in reporting gives teams ways to review project progress without assembling every view separately.
- Repeated manual actions slow routine work. Automation can handle supported repetitive workflow actions, giving team members more time for design review and delivery.
- Teams need a familiar workflow transition. Jira-compatible workflows can help teams carry established issue-management practices into ONES Project.
- Too many add-ons complicate administration. Native capabilities can reduce reliance on plugins for supported project needs, simplifying the number of extensions a team manages.
- Network requirements limit hosting choices. Cloud, on-premise, private cloud, and air-gapped deployments let organizations choose an environment that fits their constraints.
ONES.com offers a free plan for up to 30 seats. The self-hosted version has full feature parity with the cloud version, which can help teams compare deployment options without giving up feature access.
Application scenarios
Product teams coordinating design and delivery: A team can manage work in ONES Project and keep product guidance in ONES Wiki. Designers can share Figma links through the team’s chosen workflow while issue owners track related delivery tasks.
Organizations with restricted networks: A team with strict hosting requirements can assess on-premise, private cloud, or air-gapped deployment options. Its administrators can evaluate which environment fits internal access rules.
Teams reducing extension overhead: A project group can review whether built-in reporting, custom workflows, and automation cover its needs before adding more project-management plugins.
Common Figma and Jira Setup Challenges
- The app installation option is missing. Your Jira role may not include app-management permissions. Ask a Jira administrator to confirm who can install or approve the integration.
- The design link opens an access request. Jira permissions do not grant Figma access. Check the design’s sharing settings and invite the intended collaborators through the approved process.
- The link appears without a useful preview. The app version, link format, or Jira environment may affect how a link renders. Confirm compatibility and try the app’s supported linking method.
- Teammates cannot tell which design is current. Agree on a place for the active link and update it when the design changes. Use issue comments to clarify significant review updates.
- The app does not connect in a restricted environment. Ask your administrators to check network rules, deployment support, and app permissions. Do not assume that a Cloud app behaves the same in a self-managed Jira environment.
Frequently Asked Questions
Do I need administrator access to install the Figma for Jira app?
Often, app installation is limited to Jira site administrators, though permissions vary by organization. If you do not see an installation option, ask your Jira administrator whether the integration is approved and who can enable it. You may still be able to add a Figma link to an issue without installing an app, depending on your Jira setup.
Why can I open a Figma link when my teammate cannot?
Your Figma account may have access that your teammate does not. Jira project membership and Figma design permissions are managed separately. Ask the teammate to open the link while signed in to their own account, then review the design’s sharing settings and workspace access. Avoid assuming that a visible Jira preview means every issue participant can open the design.
Can I add a Figma link without installing the app?
In many Jira setups, you can paste a Figma link into an issue description or comment. Whether Jira turns it into a preview or embed depends on the environment and integration support. Try a link on a test issue and confirm what collaborators see. If your team needs additional app features, ask an administrator to check the available integration options.
Where should I put the Figma link in a Jira issue?
Place an important, current design link somewhere predictable, such as the issue description or a designated field. Use a comment when the link is temporary or part of a review conversation. The best choice depends on how your team reads issues. A consistent convention matters more than a particular location, because teammates need to know where to look.
Does the integration work with every Jira deployment?
Compatibility depends on the app and your Jira environment. Cloud and self-managed Jira deployments can have different app support, permissions, and network requirements. Check the app’s current compatibility details with your Jira administrator before planning a rollout. If your organization uses a restricted network, include that requirement in the compatibility check.
Conclusion
Setting up the Figma for Jira app comes down to confirming compatibility, enabling the right integration, sharing the correct design link, and testing access with a teammate.
But here's the truth: installation is only part of a dependable setup. A clear linking convention and correct Figma permissions help keep designs useful inside Jira issues.
Start with one issue, verify the experience, and adjust your team’s process before expanding it. If you are also reviewing how project work and team knowledge fit together, ONES.com may be worth assessing alongside your design workflow.