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

[G subramanyam · Accepted solution]

Hi @Katja Arendt welcome to the Atlassian community.

Please bookmark this Jira Product Discovery resource link and keep watching for content that will be added.

[Katja Arendt]

Great thank you ;)

[Tanguy Crusson]

Hi @Katja Arendt , thanks for asking! We're working on it but it's not ready yet. What are you hoping to get from it?

[Katja Arendt]

Hi, I really celebrated your videos where you explain how you use JPD in your team. In the end, you realise that people who use JPD often face the same challenges. What I hope to see in the handbook are best practices and examples of use. Of course there is a lot of talk about this here in the community, but I would like to see the most common examples in a handbook like this. This ranges from the general structure and layout to what kind of fields are used how to get the best result. And all of this also under aspects such as how one can best incorporate Jira automations here to automate common processes or best practices in interaction with other Atlassian products such as Jira software and Confluence. I hope that was understandable :)

In general, I am very interested in exchanging ideas with other people who are responsible for coordinating projects or managing requirements for several different systems in their company.

[Katja Arendt]

PS: I was also very surprised that you don't use the "Delivery" function to track progress. When I started working with JPD, that was one of the reasons why I said that's what we needed. But I find your approach very interesting and it made me think about why it is actually so important for us to monitor progress in this level of detail.

[Tanguy Crusson]

Thank you for the context @Katja Arendt ! that's super helpful

[Tanguy Crusson]

Anecdotally, we saw that teams start using Jira Product Discovery because of this delivery integration, and we see it as a great way to get people interested in trying the product. But we want to try and recommend more sustainable ways to manage stakeholder expectations wherever possible after that 🙂

[Deyan Genovski]

Looking forward to this handbook @Tanguy Crusson