Tanguy Crusson Atlassian Team

Hi @Helena Jeret-Mäe , not yet - the same solutions are still what we recommend today. 

@Patrick Blackburn what you see is what you get today: * you can customize the form * but it only shows if you're in the project What issue collector do you use otherwise? wondering if you could reuse that to point to a Jira Product Discovery project

Thanks for the feedback Rob. It makes complete sense. For tagging customers on ideas, we're currently looking at another solution which is to leverage the "Customer/Organization" fields from Jira Service Management - which can (or will) be synced with Salesforce (and I believe - could be wrong, need to check - HubSpot)

@Davina Pallone @Rohan Swami I think you should be able to do it from the group instead. Open the group, and see if there's an option to remove product access for Jira Product Discovery from there.

Here you go:

Hi Rob, What were you hoping to achieve in Jira Product Discovery with HubSpot? To be honest his is not on the roadmap for the moment - the main reason is lack of demand for now (which plays a big part in how we prioritize): we only had 4 requests about this so far including yours. 

Done. Reminder: if I hit "like" to your message, it means you got access

Here: 

Forever is a really long time, I wouldn't go that far 😂 Otherwise the other fields will eventually be supported by the API and Automation - I'll spare you the details but basically we built them in a way to be able to experiment quickly, and now we're in the process of moving them to a better solution inside Jira to…

Hi, Today Jira Product Discovery is a prioritization and roadmapping app. The "Votes" field in Jira Product Discovery (JPD) was optimized for point-in-time voting: you share a view to a list of people, you give them a budget, and they allocate this budget among a list of ideas. It's meant to be used as a way to start the…

Hi Mart, I wish it was an easy fix 🙂 It's not, and we have prioritized other things for now. This fits in the theme of "sharing" where we have a team fully committed, and they have prioritized: * Read-only sharing with anyone inside our outside your company (the early access program is progressing well there, but still a…

ok, thanks for the feedback 👍

Great, thanks for the context. And just to confirm, you've seen this, and this is not enough. Correct?

Okay, we got to the bottom of this, I can confirm the following: Email notifications will work when an issue is updated by a contributor who has access to any Jira product (Jira Software, Jira Service Management, Jira Work Management, Jira Product Discovery) But not if it's done by a contributor who has got no access to…

Okay, that makes more sense now, thanks Maria 👍 If creators are not receiving notifications then you should definitely raise a support ticket - that is meant to work (we just tested and it does work in our test sites) As for contributors: they do not receive email notifications yet, something we'll need to get to. (edit:…

Ah okay, that's a different issue to how I understood it based on your post above. So, it's not that notifications were working one day and stopped working the next, correct? But that you'd like contributors (people without a Jira Product Discovery license) to receive email notifications. Did I get this right? Or is it a…

Hi @María Ferreño Serra , we might need to get in your site to investigate this, and that requires a support ticket. Could you please create one? it's easy, from JPD, "Give feedback", choose the support option, paste the same thing there, and voila.

Hi Julia, this isn't something we're currently planning to do but I've added this to the list of feedback for that feature (we're currently working on improving it)

Hi Holly, it's definitely something we'll do (it's on the ever expanding list of top feedback - when will it ever shrink? 😅), but by the time we're done it and ship it, it might be too late for you if you are in the middle of the move now 🤨

Hi @Owen Scott , to be perfectly honest this is unlikely to be something we prioritize in the medium term. It is not in the top 20 things that came up in the past few months. 

Hi, this feedback came up frequently in the past few weeks. We're currently working on adding the filter and sort menus to all views so that contributors can use them. It's not going to let them view or change existing filters, but they'll be able to filter down further the list of ideas in that view, without saving that.…

Hi Jens, not currently, but thanks for the feedback! How many people are you sharing your views with?

@Ohyoon.Kwon you can make the template filled in by default when clicking on the blue "Create" button in the Jira top navigation bar. To do this, go to Project Settings > Features > Create idea

HI all, sorry I thought I did this earlier 🤔 here's a github repo with an example for how to use the API for creating insights: https://github.com/Atlassian-integrations/polaris-forge-ref-app/tree/master/push-example

Hi @Jack Arndt , Thanks for bringing this to our attention. It sounds like we put the cart before the wheel here, and released a change before we communicated it properly. It's been reverted and your status description should be back now. However, this will only work like that in the short term (another 2 weeks), to give…

Hi, if you click here you should see the details of who's opened the view when (top-right in every view)

Hi @Louise Baker , Jira Product Discovery wasn't really designed to be a "feedback portal", however this is something we were considering as a future enhancement (for search, or when viewing an idea)

Hi @Selvameenakshi Viswanathan , thanks for the feedback. It is not possible currently but I've added that to the idea we use to track filtering improvement requests.

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

@Julia Titeux it took a bit longer than we were expecting, but it's now fixed! Can you please confirm it's working fine for you now?