has anyone ever got a jiraServiceManagement:portalRequestViewAction module running on Custom UI? I assume this module is broken. Deployments of an according manifest.yml are rejected by Forge servers.
minimal manifest.yml to reproduce (app id removed):
I can confirm that the module is now working as intended. The modal is opening, the Custom UI gets rendered. I’ll keep you updated in case we will stumble across other blockers. Thank you for the quick assistance on that. Really appreciate it!
After digging deeper we unfortunately ran into another roadblock here. The modal of portalRequestViewAction is missing any context information. There is no way to find out the issueKey of the according ticket where the modal was opened from. So there is no possibility to show any request related information or actions which makes the module barely useful.
Extension context of portalRequestViewAction
Extension context of portalRequestDetailsPanel
Would you please report this to the development team?
thank you for raising that ticket. We would expect the same context information as in the other modules (like portalRequestDetailsPanel). portalId, requestKey and typeId are required to offer more functionality which correlates to the request where the portRequestViewAction was opened from.
Do you have any time estimation on when this will be fixed? Any information would be appreciated as we’ve to decide whether to start a new project on Forge or Connect.
@JulianWolf the team is reviewing what is needed to add the additional context.
No promises but, if everything goes well, it should be available in less than a month. Any updates will be posted on the ticket and you can ask there for an update as well.