Limitations for Forge app when calling createmeta?

[Martin Sereinig]

hey there.

we're trying to create ideas through our forge app, but for some reason the forge app doesn't see the Product Discovery projects when trying to createmeta to get the field configuration.

we've tried the following:

/rest/api/3/issue/createmeta?projectIds=whatever&projectIds=whatever

/rest/api/2/issue/createmeta?projectIds=whatever&projectIds=whatever

to debug – we've also tried to remove all filters, but even then we only see projects that are not Product Discovery. so it seems like those project types are invisible to our createmeta calls.

we've also tried to do this:

/rest/api/2/issue/createmeta/${projectId}/issueTypes/${issuetypeId}

but in this case, the api tells us: "OAuth 2.0 is not enabled for method". we're pretty sure this used to work and we haven't changed the code on our side. is this to be expected? what can we do?

we also have an integration that works based on a normal oauth flow, and there it does work – we can see product discovery projects and also post ideas. 

thanks for your help!

martin

[Bill Sheboy]

Hi @Martin Sereinig 

You may want to also post this question in the developer community.  I did a quick search and did not find any similar ones.

https://community.developer.atlassian.com/tag/jira-product-discovery

Kind regards,
Bill

[Martin Sereinig]

hey bill! thanks for pointing that out. i'll do just that.

[Tanguy Crusson]

Looks like someone answered there: https://community.developer.atlassian.com/t/jira-product-discovery-limitations-for-forge-app-when-calling-createmeta/73169/2