TypeError: Invalid attempt to iterate non-iterable instance. (forge custom ui)

Forge Forge UI Kit and Custom UI
1

Hi there,

i am facing a really strange behaviour in the same jira instance

Lets say i have an epic with key PS-1 and it has some child issues PS-2,PS-3.
I am getting a strange error log in production when i am iterating the issues of that epic.

TypeError: Invalid attempt to iterate non-iterable instance.
In order to be iterable, non-array objects must have a [Symbol.iterator]() method.
    at a (createForOfIteratorHelper.js:26:11)
    at Iw (App.js:58:4)
    at ei (react-dom.production.min.js:153:146)
    at Gi (react-dom.production.min.js:175:309)
    at Cc (react-dom.production.min.js:263:406)
    at Ol (react-dom.production.min.js:246:265)
    at Sl (react-dom.production.min.js:246:194)
    at hl (react-dom.production.min.js:239:172)
    at react-dom.production.min.js:123:115
    at t.unstable_runWithPriority (scheduler.production.min.js:19:467)

The most strange part is that when i am iterating the issues of an epic of another project e.g DSM-1 with child issues DSM-2,DSM-3 , then everything is running as expected, the issue-panel opens and everything is running smooth.

Unfortunatelly i can not reproduce it in Development or Staging environments. :expressionless:

Any help with this one? or anybody had the same problem in the past?

2

Replying to myself and maybe others who may have this issue.

I found that the project role atlassian-addons-project-access was missing from the projects permission scheme.

This is something really bad and this is a topic that Atlassian should take care of.
This group/role is important to apps and should not be available to be edit by anyone as it seems. I dont get why this group/role should be visible to us (admins) and available, while it should just be “secret”

Atlassian Ecosystem Design atlassian-plugins Jira Cloud