Is there an API to migrate ideas+insights from other product management solutions?

[Guy Yasoor]

Hi,

I'd like to migrate my team to JPD, but I wouldn't want to lose all the features and insights we already categorized in our current product!

For that, I need an API where I can create ideas and link insights to them. (unless of course someone has a better suggestion!)

I've checked the forum and only saw a few comments about the Jira Issue API being available for Idea creation - but I'm guessing I can't add insights from there?

So is there a hidden API available, or a date where we can expect it?

Another issue I have is with insights' position in general - I'd really like them to be separate entities that I could create, and only later link to Ideas - this is also sort of blocking us from migrating. If anyone can shed light on this it would be great, as I've seen multiple people asking for this in the forum).

Thank you!

[Tanguy Crusson · Accepted solution]

@Guy Yasoor @David Bakkers we do have an API for insights

[Guy Yasoor]

Thank you @Tanguy Crusson ! I'll check this out.

And currently I can only add insights to existing ideas, right? Are there any news about creating insights that aren't connected to any idea yet?

[Tanguy Crusson]

@Guy Yasoor not yet, we're unpacking the jobs of dealing and managing feedback currently, but it's all in whiteboards, not code 🙂

[Guy Yasoor]

Thanks!

Just to explain my situation further - hope this helps:

In my company, internal stakeholders (sales, support, etc.) submit feature requests as Productboard insights. We also submit customer FRs as insights.

Then, we have a process in the PM team, of "triaging" these insights to existing/new "features" (AKA ideas).

I don't expect my customers or salespeople to connect the insights to ideas themselves, since there can be hundreds of ideas, and they're not deeply familiar with all of them. So I prefer that they submit "raw text" and that I connect it to my features.

I couldn't find a good alternative workflow in JPD currently, still trying some things out, but I think independent insights (that can be created by non-creators) would solve this for me.

Would also be happy to jump on a product discovery call if you're interested.

Thanks again for the quick response :)

[Tanguy Crusson]

@Guy Yasoor I see. This is what we have in the FAQ for this scenario. Our current recommendation is #1 - that's the one that scales better.

How can we use Jira Product Discovery to collect feedback from customers/users and other teams (support, sales, customer success, marketing)?

In this first version of Jira Product Discovery, we’ve focused on some the jobs that help a PM do their job: prioritizing ideas and opportunities, creating and sharing roadmaps that stay up to date, and capturing feedback from a bunch of different places (interview notes in Confluence/Google Docs, conversations in Slack/Teams). But for now we assume the PMs have existing channels they use to receive feedback, and we help them send this feedback to ideas in Jira Product Discovery.

We have only partially tackled the job of creating a direct feedback channel between customers/users or other internal teams (sales/support/customer success/marketing) with the product team. We have plans to do more there, but for now these are the options that you can use to do that with the product today:

1. Set up a Jira Service Management queue to receive feedback from customers and internal teams

2. Set up a dedicated Slack channel #product-feedback to receive feedback from internal teams (also works with Teams)

3. Share views with other teams and gather their feedback using fields and votes to receive feedback from internal teams

[Guy Yasoor]

Thanks @Tanguy Crusson . The service management queue might be a viable solution for us - I'll test this out.

Back to the API - the "create insights" example doesn't seem to work for me - is there anyone I can contact about this?

[Tanguy Crusson]

@Guy Yasoor if you could share a few details about what's not working I can ask someone from engineering to help.

[Guy Yasoor]

@Tanguy Crusson So at first I had a bug with `ts-node`, but I solved it by upgrading the version, like explained here - https://stackoverflow.com/questions/72488958/false-expression-non-string-value-passed-to-ts-resolvetypereferencedirective. I suggest updating it in the repo too?

Now I'm having problems with the Authorization URL - tried `localhost:7777` with both HTTP and HTTPS:

- `https` is what the README suggests, but when entering the auth URL, `id.atlassian.com` says "we're having trouble logging you in".

- `http` allowed me to authorize the app, but then when getting redirected to localhost, I'm getting "localhost refused to connect." in Chrome. And in the CLI, I get the error "Error: Failed to fetch issue. Status 401: Unauthorized".

[Tanguy Crusson]

@Guy Yasoor we just fixed something in the sample app, can you pull the latest version and try again?

[Guy Yasoor]

@Tanguy Crusson Working now - thank you!

[yasmin.desai]

+1 on having insights that aren't connected to any idea/feature. I don't see why they need to have a 1:1 relationship!

[David Bakkers]

"So is there a hidden API available"

Nope. As per this thread, there is no JPD specific REST API yet.

[Guy Yasoor]

@David Bakkers I've seen some contradicting comments though - here I see an API mentioned for insights creation.

[David Bakkers]

If you believe that thread describes an API that is specific to JPD and is specifically for creating insights, then I suggest you follow the instructions on that thread on how to access and use that API, or contact the Atlassian staff member that advised of the existence of the API.

Good luck on your learning journey