Hi, I’m trying to test out the example app here: Bitbucket which we’ve used forge install and forge deploy to deploy to our confluence environment
We thought it would work as is, but with api.asApp functionality we believe it doesn’t have enough authority to retrieve projects/issuetypes like it needs to (as asApp only inherits default user permissions), but then when trying to do api.asUser, it wants to request access while configuring the macro, but when we click the Allow Access button, it does not work - we think this may possibly be a bug in Forge?
Cheers
Zac
https://ecosystem.atlassian.net/browse/FRGE-239
Created a ticket cause this developer area was set to readonly and couldn’t provide update here
Hi @zacmetinxero
One thing you may have missed is that you need to install the app into Jira as well as in Confluence. This should allow the app to fetch issues/projects via asApp.
If you need asUser for your permissions… at the moment, Forge macros aren’t interactive in edit mode, so what you’ll need to do is to first insert the macro, then publish the page, then click the “Allow Access” button and complete the auth flow. Once you’ve done that, you should be able to go back into edit mode and configure the macro. Note that in this case, you’ll want to edit the code to first make a request that requires user authentication during the main UI flow (not config). This will then trigger the “Allow Access” button to show up.
Let me know how it goes!
Hi Ryan, that worked thanks
1 Like
