Jira 9 deferred resources issue view vs global issue navigator / backlog view

We’ve been working on Jira 9 compatibility for one of our apps and we’ve ran into an issue with the deferrd resources which seems are handled differently in issue view compared to global issue navigator or backlog view.

We followed the suggestion in the Preparing for Jira 9.0 → App header updates and added the attribute type="module" to our javascript code.

This works in issue view and the code is deferred automatically but it doesn’t work in global issue navigator or backlog view. We fix this by “duplicating” the js code with these attributes “nomodule defer” to make it work in global issue navigator or backlog view.

Although it works, it doesn’t seem the most clean solution. Is there any differentiation in the way deferred resources are loaded in issue view compared to global issue navigator or backlog view?

Thanks

I think I have the same issue: [CRITICAL] Changes to Jira 9 resource bundler are creating race conditions to WRM / AJS - #11 by remie

Only haven’t found time yet to create a sample app that reproduces this for investigation by Atlassian.