Skip to main content
Solved

Figma design links are intermittently being removed from Jira tickets.

  • March 9, 2026
  • 2 replies
  • 43 views

Brian Charniga

We are experiencing an issue where Figma design links that are added to Jira tickets are later being automatically removed without user action.

This is happening across multiple tickets tied to the same epic, not a single isolated story. The behavior appears inconsistent—on some days the Figma links are visible, and on other days the same links are gone.

This has been occurring consistently for many months.

Where It’s Occurring

  • Multiple Jira tickets across Projects
  • Appears to affect Figma file links specifically

Observed Behavior

  • Figma links are successfully added to Jira tickets
  • At a later time, the links disappear
  • Some users can still see designs while others cannot
  • The issue does not appear to be permission-related or user-specific; Designs can show up fine one day, but then disappear for the same user

Expected Behavior

Figma design links added to Jira tickets should persist and remain visible to all users with access to the ticket.

Impact

  • Engineers, QA, and stakeholders cannot reliably access Figma design references from Jira
  • Designers are repeatedly asked to re-share links

Best answer by djv

Hi ​@Brian Charniga, thanks for flagging this issue! 

Have you flagged this issue to Atlassian support yet?  The Figma for Jira integration is co-owned by Figma and Atlassian. For any issues with Jira functionality, it’s best to contact Atlassian Support directly, as the functionality is owned and maintained by Atlassian. There were similar reports of this bug in the past that were fixed previously, so this may be a new regression. 

2 replies

djv
Figmate
  • Community Support
  • Answer
  • March 12, 2026

Hi ​@Brian Charniga, thanks for flagging this issue! 

Have you flagged this issue to Atlassian support yet?  The Figma for Jira integration is co-owned by Figma and Atlassian. For any issues with Jira functionality, it’s best to contact Atlassian Support directly, as the functionality is owned and maintained by Atlassian. There were similar reports of this bug in the past that were fixed previously, so this may be a new regression. 


Brian Charniga

Thanks, I’ll go there then!