Jira app feedback

I wanted to offer feedback around some of the reasons our company decided to remove the Figma app from Jira. There are a few things missing or mis-matching between our use of Figma and Jira.

Figma is mostly used for software UI design but our DevOps team also use Jam for flowcharts sometimes, Marketing use it for some web and email design work.

Jira is also used by several teams in the company, all of the above mentioned ones + several more.

This causes some issues with how the “Jira app” is structured.

  1. You can setup the app to link to 1 and just 1 team in Figma. But this links to all of Jira. Not to any one team or project in Jira. We would want 2 Figma teams linked to 3-4 Jira projects.
  2. The app is not useful in any other Jira project but we were still not able to figure out how to disable the UI added onto all Jira cards. (E.g. “Add a Design” button)

In contrast, apps like the one for Slack, Checklist pro, or MS Teams are apps you configure per Jira project. I can also link a specific Slack channel to a specific Jira project for example.

It might seem like picking nits but with many users of our Jira being “casual” users… not hardcore Jira experts, any added complexity or clutter from apps does add up after a while. This does start to degrade the experience for the majority of users in order to benefit a minority (e.g. designers and developers).

We still use both Jira and Figma… but now we simply paste share links into Jira the way we used to before we added the app.

cheers,
Martin

Hey Martin, thanks for your detail feedback! We’ve passed it along to our team for consideration.

“You can setup the app to link to 1 and just 1 team in Figma. But this links to all of Jira. Not to any one team or project in Jira. We would want 2 Figma teams linked to 3-4 Jira projects.” => Can you clarify and confirm if you are running into an issue where you can ONLY link 1 Figma team? (you should be able to link multiple teams)
Thank you!

As @Martin_Westin mentioned, this would be better if the app was able to be configured per-project at a local Jira project admin level where our PM’s have access, instead of having to be configured by a full Jira administrator.