Collecting ideas from external users in external places
Asked by Martijn ten Caat:

I would like to collect ideas from our own community software from users that don't have an Atlassian-account, is there a way to collect via API of via an embed-able form?


Answers:
author: Owen Friedrich
body: We use Salesforce Community Cloud for our customer community - specifically the Ideas module to collect product feedback. When ideas are added we also send them over to JPD using a Boomi integration process that utilizes the Jira API. There is also some bi-directional sync setup to update the status of the idea in the community.


author: Jonathan Blackburn
body: There have been some clips where this has been discussed.

I think it's worth considering whether you want to allow everyone to do this and the impact it would have on your idea backlog integrity. Might be good to gather feedback first through something like JSM before then entering into JPD like the JPD team do (<https://www.youtube.com/watch?v=Yp0q7YVYM4c>)

On API here's what they have in their FAQs (<https://community.atlassian.com/t5/Jira-Product-Discovery-articles/Frequently-asked-questions-about-the-product-how-do-I/ba-p/2002378>)

**Does Jira Product Discovery have an API?**

There are a few things we need to iron out so you can query all information via an API, however, there's already a great deal you can do today:

* Jira Product Discovery **ideas** are Jira issues, so you can query them using the [Jira Cloud Platform REST API](https://developer.atlassian.com/cloud/jira/platform/rest/v3/intro/)
  * This will return all fields except dynamic fields (e.g. formula fields).
  * But things like status, multi-select/select, number, date fields, etc. will just work
* We have a [public API for **insights**](https://github.com/Jira-Product-Discovery-Integrations/polaris-forge-ref-app)
* We don't yet support a public API for **views**

So that should be more than enough to let you create reports to show how many ideas there are, who's working on them, what status they're in, how long they've been in the project, when they were last updated, etc.

One team let's people enter it directly but that's a LOT of ideas potentially - <https://www.youtube.com/watch?v=o8R0cc3jzBU>


author: Rob Mkrtchian
body: I know there is an app that allows embedding public roadmap. It's called Released.so and you can download it on marketplace. Public roadmaps product are in beta, they might give you an access soon.  

FYI. [@Jens Schumacher - Released_so](/t5/user/viewprofilepage/user-id/3653468) @jensshuma

comments: author: Jens Schumacher - Released_so
body: Thanks for the shoutout [@Rob Mkrtchian](/t5/user/viewprofilepage/user-id/5465093)!  

[@Martijn ten Caat](/t5/user/viewprofilepage/user-id/4665932) feel free to get in touch if you want to learn more about Released.   

We are building out public roadmap sharing as we speak. Collecting feedback will follow shortly after.   

You can sign up for the beta here: <https://www.released.so/roadmaps>  

<br />


author: Tim Maynard
body: how are the released.so roadmaps different than publishing a view straight from JPD?


author: Jens Schumacher - Released_so
body: [@Tim Maynard](/t5/user/viewprofilepage/user-id/5507795) there are a few ways Released roadmaps differ:   

<br />

**Anonymous access**

Viewers don't need to log in and don't require an Atlassian account to view the publicly published roadmaps.   

**Cross-project**

You can publish a roadmap that includes ideas from multiple JPD projects or even Jira Software projects, all on one board.   

**Embeddable**

You can embed Released roadmaps in your website to make it easier to find for customers. Here is an example: <https://www.trypencil.com/release-notes?released=roadmap>  

**Custom columns**

The columns in Released don't have to adhere to the field options. Meaning you can customize the columns to best suit the public communication.

**Different look and feel**

The cards look a little less like Jira.   

And we will be adding more features in the coming months, such as the ability to collect feedback directly on the roadmap.   


author: Martijn ten Caat
body: Hi Jens, thanks for the response. As much as I might like the solution you're offering, I don't like the fact that I need a third party tool for something I expect JPD to have in their toolbox.

Also, it feels like paying double, I feel like this should be part of the subscription from Jira.


Tags: collect

embed

ideas

jira-product-discovery