Im having an problem creating issues from Sticky notes in a Figjam Board
What is strange is I was able to create the first three without any error
As I proceed to create the rest, I now get an error in Figjam board "Unable to create issue"
Nothing has changed on the project; there are no new required fields.
Hi Christine,
That’s definitely a valid situation — you were able to create a few issues from sticky notes in a FigJam board and then hit an error saying “Unable to create issue”.
Here are a few areas to check which often cause this behaviour:
Required fields or metadata changed
Even if there were no recent manual changes, your Jira project may have added a new required field after the first few issues were created.
→ Check Project settings → Issues → Fields → Required fields to see if any new field appears in the create screen.
If the FigJam plugin doesn’t provide a value for that field, the “Create issue” call will fail.
Permissions & issue-type restrictions
The sticky-note creation uses the Jira Widget or FigJam plugin, which authenticates you and uses the Jira Cloud REST API under the hood. (static.figma.com)
If your permissions changed (for example your service desk license removed, or issue-type no longer available), you’ll also see this error.
→ Try manually creating an issue of that same type in Jira to validate you still have rights.
Project or board mapping for stickies
In FigJam, when you select “Turn stickies into issues”, you must select the correct project and issue type from the dropdown. (help.figma.com)
If you inadvertently switched to a different project or changed the dropdown earlier for the first ones, then for later ones it may default to an invalid combination.
→ Make sure the project + issue type are valid and that the workflow is active.
Rate limits or plugin glitches
Occasionally if many issues are created in rapid succession, the integration may hit rate limits or timeouts and fail silently.
→ Check the browser DevTools console in the FigJam board for any error message when the failure happens.
→ Also ask your Jira admin to check the Atlassian logs (Audit log) for any rejected API calls.
Maybe you should contact app's support team so they can assist you with this use case. Which app do you use?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.