@vpetrychuk is there somewhere to track progress on support for custom fields in the CreateIssueModal? This will be big for us, as we’re heavily reliant on custom fields.
Hello @vpetrychuk.
I’m trying to use the ViewIssueModal just like the example but I get this error when call viewIssueModal.open();. Can anyone help me?
Uncaught (in promise) Error: Unable to open issue create modal.
at ViewIssueModal.<anonymous> (issue-view.js:32:1)
at Generator.throw (<anonymous>)
at rejected (tslib.es6.js:74:1)
I inspected the error and got:
"Error: No handler found for post message: openIssueViewModal from http://localhost:8001 in https://my-instance.atlassian.net/jira/apps/20d37b86-8cfd-449a-a5c4-63e2e607b49f/1dac9e5d-8be9-4309-a97f-2651ad4b42fa/issues-risk/19a520af-4435-4e75-a825-3d92f1ebd99a
at https://jira-frontend-static.prod.public.atl-paas.net/assets-brotli/async-forge-ui-iframe-full-page.762db20321bc49f31c2b.8.js:671:606
at Function.e.try (https://jira-frontend-static.prod.public.atl-paas.net/assets-brotli/async-forge-ui-iframe-full-page.762db20321bc49f31c2b.8.js:651:369)
at Fe (https://jira-frontend-static.prod.public.atl-paas.net/assets-brotli/async-forge-ui-iframe-full-page.762db20321bc49f31c2b.8.js:671:581)
at Ne (https://jira-frontend-static.prod.public.atl-paas.net/assets-brotli/async-forge-ui-iframe-full-page.762db20321bc49f31c2b.8.js:673:778)
at https://jira-frontend-static.prod.public.atl-paas.net/assets-brotli/async-forge-ui-iframe-full-page.762db20321bc49f31c2b.8.js:680:66
at Function.e.try (https://jira-frontend-static.prod.public.atl-paas.net/assets-brotli/async-forge-ui-iframe-full-page.762db20321bc49f31c2b.8.js:651:369)
at https://jira-frontend-static.prod.public.atl-paas.net/assets-brotli/async-forge-ui-iframe-full-page.762db20321bc49f31c2b.8.js:679:828
at https://jira-frontend-static.prod.public.atl-paas.net/assets-brotli/async-forge-ui-iframe-full-page.762db20321bc49f31c2b.8.js:680:115
Error: No handler found for post message: openIssueViewModal from http://localhost:8001 in https://my-instance.atlassian.net/jira/apps/20d37b86-8cfd-449a-a5c4-63e2e607b49f/1dac9e5d-8be9-4309-a97f-2651ad4b42fa/issues-risk/19a520af-4435-4e75-a825-3d92f1ebd99a
at hn.error (https://forge.cdn.prod.atlassian-dev.net/global-bridge.js:1:19406)
at Object.<anonymous> (https://forge.cdn.prod.atlassian-dev.net/global-bridge.js:1:27179)
at JSON.parse (<anonymous>)
at o (https://forge.cdn.prod.atlassian-dev.net/global-bridge.js:1:27038)
at jn (https://forge.cdn.prod.atlassian-dev.net/global-bridge.js:1:27191)
at Tn.u.on (https://forge.cdn.prod.atlassian-dev.net/global-bridge.js:1:31851)
at Tn (https://forge.cdn.prod.atlassian-dev.net/global-bridge.js:1:31988)
at https://forge.cdn.prod.atlassian-dev.net/global-bridge.js:1:37974
at Function.n.try (https://forge.cdn.prod.atlassian-dev.net/global-bridge.js:1:10458)
at https://forge.cdn.prod.atlassian-dev.net/global-bridge.js:1:37771
at r (https://forge.cdn.prod.atlassian-dev.net/global-bridge.js:1:38023)"
Adding custom fields support is one of our top priorities for the upcoming sprints.
Once the feature is ready we will announce it on this portal and add an entry to the changelog in Forge docs. Please track those resources and here’s the issue to watch: https://ecosystem.atlassian.net/browse/FRGE-494
At the moment it is not possible to open the issue view modal from the issue view page without experiencing weird bugs. As soon as we fix that, all the modules on the issue view will be able to open it. Unfortunately, this is not our top priority at the moment. The list of supported modules could be found on ViewIssueModal page.
We’ll update the documentation clearly stating that extensions on issue view aren’t supported and update the error message so it is clear.