Is it possible to create app that generates templates for Jira Product Discovery?

This is going to be my first app for Jira ecosystem, thus sorry if this question might sound rookie. And I loved JPD for its flexibility and with flexibility there is uncertainty, therefore I decided to create app that will allow JPD users to apply various templates. Now I assume that at least the first prerequisite must be an ability to create new view there, and I couldn’t find “POST” endpoint for creating a view.

Can you please tell me if it is possible to build such app technically-speaking and if it is, where I should start?

Thank you in advance.

@Robert_Mian,

It’s nice to meet another JPD fan. I’ve used it for a few projects myself and understand the balance of flexibility.

To answer your question, unfortunately, no, there aren’t any REST APIs specific to JPD, which also means nothing would let you manipulate the JPD-specific UI constructs like views.

I recommend logging a feature request so you, and others who might stumble upon this thread, would have something formal to track. Could you please open a “suggestion” (our term for feature request) issue yourself in our open Jira (JAC) in the ECO project . Once you have the issue key, please let us know here so other folks can watch, vote, and comment (including me).

Hey @ibuchanan

Thank you for responding to my request. I have created a suggestion in JAC, here is the link:

https://jira.atlassian.com/projects/ECO/issues/ECO-255

I’m not sure tbh view creation and other manipulation is better to handle with REST API or functions, therefore I added both as components to suggestions. Hope it will get resolution soon.

1 Like

Hi @ibuchanan ,

May I ask what happened to the ECO project issue I created after our conversation? It doesn’t display on the project board. Thank you!

This was the link: https://jira.atlassian.com/projects/ECO/issues/ECO-255

@Robert_Mian,

I don’t see anything wrong. I don’t know about any “project boards”. Atlassian teams don’t run sprints out of JAC directly, so there won’t be any Sprint board. Could it be a problem with login to JAC? Even though JAC is public, I think you might need to be logged in to see ECO issues? I don’t think it’s a problem but the canonical link is: https://jira.atlassian.com/browse/ECO-265

Sorry! It’s some link redirection problems. After writing my response, I realized the issue keys don’t match up. I think the project link you have is redirecting incorrectly; hence, the canonical link is the problem here. Use: https://jira.atlassian.com/browse/ECO-255 (which oEmbed reads incorrectly now and gets rendered as a login link by Discourse).

That should redirect you automatically to where the issue was moved, which is into JPD’s project: https://jira.atlassian.com/browse/JPD-182

To my knowledge (and something I’ve gotten wrong recently), only ECO is open for public feature requests; hence, the need to report it first in ECO.

@ibuchanan thanks for prompt response. The link you suggested to visit: Log in with Atlassian account

Shows “You can’t view this issue” message.