Tanguy Crusson Atlassian Team

Hi! we now have a new answer for this if you're using the Premium plan of Jira Product Discovery - you can use it to manage discovery tasks: https://community.atlassian.com/forums/Jira-Product-Discovery-articles/New-manage-discovery-tasks-in-JPD-needs-the-Premium-plan/ba-p/3044161#M3421

Hi! we now have a new answer for this if you're using the Premium plan of Jira Product Discovery - you can use it to manage discovery tasks: https://community.atlassian.com/forums/Jira-Product-Discovery-articles/New-manage-discovery-tasks-in-JPD-needs-the-Premium-plan/ba-p/3044161#M3421

Hi! we now have a new answer for this if you're using the Premium plan of Jira Product Discovery - you can use it to manage discovery tasks: https://community.atlassian.com/forums/Jira-Product-Discovery-articles/New-manage-discovery-tasks-in-JPD-needs-the-Premium-plan/ba-p/3044161#M3421

Hi! we now have a new answer for this if you're using the Premium plan of Jira Product Discovery - you can use it to manage discovery tasks: https://community.atlassian.com/forums/Jira-Product-Discovery-articles/New-manage-discovery-tasks-in-JPD-needs-the-Premium-plan/ba-p/3044161#M3421

@Kathrine Lønning 😭😭😭 I'm actually hoping we don't go there and help companies inflict this pain on PMs 😂

Here are 2 ways to do it directly in the UI: If you want to copy values between 2 fields in the same project (for example to move from a select field to a multi-select field) , you can use the "bulk edit" functionality in list views: Demo: copy field values using bulk-edit. If you are using a Project Field in a project and…

Hi @Tatiana Torset - yep we're on it! We're currently working on support for connection fields in Published views. It's coming very soon. 

@Kevin Hoffman that's a limitation/challenge with the model we went with and we're discussing options to best address it 👍 @Antal Vig _ Communardo We're keen to hear back what you find out if you try that out - I've tried myself and am not sold that it will quite cut it for an insights solution, but it was only a very…

@Lisa McCann it really depends on how you approach it. Here's one scenario where different types and insights can work together (that some teams we worked with are using) * Something starts as an idea, and the PM keeps adding new insights as they learn more about it, passively, every once in a while. * As it firms up it…

We've started working on this: it's not about hiding fields but letting you configure pinned fields for each type. Would that work? You can always collapse the "other fields" section (and it should stay collapsed).

@Lisa McCann Different teams do it differently - but in the JPD team we don't really use data points on capacity and time/effort for the product trio (every PM/designer/eng lead has a bunch of topics in flight for wonder/explore stages but we don't really track it in a system - we discuss those when we meet twice a week).…

Hi @Ilona Borsos , yes you can see a mockup of it here (3rd image)

https://community.atlassian.com/forums/Jira-Product-Discovery-articles/Product-update-You-can-now-copy-project-configurations/ba-p/3029306

Hi all, this feature is live: https://community.atlassian.com/forums/Jira-Product-Discovery-articles/Product-update-You-can-now-copy-project-configurations/ba-p/3029306

perfect thanks!

Hi, thanks for the feedback - we don't support this today but will look into it as we improve this feature. 

Hi, we described what you can do here: https://www.atlassian.com/software/jira/product-discovery/resources/handbook/feedback-and-insights#what-are-insights

Hi, what do you mean by "not visible"? thanks

Hi, yes, it's on the roadmap and not supported today. what you can do on Plans is group all epics by Customer Journey (the level you connect to epics)

HI @Saif Allah AZZAZA , JPD doesn't support permissions at that level for comments. Thanks for the feedback. A potential workaround is to publish the view you want to share with specific stakeholders, and hide all comments there. 

That's what the Votes field is for! What were you after?

Hi @Dan Foster have you tried creating a field of type "Votes"? That's what it's for. Or "reactions" for a more lightweight version. 

Thanks for the feedback

@bill is correct - these fields are not supported in the backend yet, they're just calculated on the frontend - hence why you can't use them in JQL, automations, etc. We have a project planned to fix that. 

Thanks for the feedback @Jonathan Prisant . We don't plan to change this yet (it's the first time this came up and we have other things with more demand) but we'll keep a watch on this!

Hi @Eduardo Calvillo just making sure you saw this first for Goals and Projects? (from the FAQ) How do I use Jira Product Discovery with Goals and Projects (ex Atlas)? Here is a demo for how to use Atlas goals and projects in Jira Product Discovery That's assuming you're using Project as per this feature and not something…

Hi, without more details I'm not sure what you're trying to do, so I've just taken a guess and suggested something here: https://www.loom.com/share/81220fe204ce498f883a48e6bbb7d475

@Mark Colonnese ah ok I see, maybe that wouldn't work if you already have JPD on your site, on another plan. In that case you can go to admin.atlassian.com > Billing > JPD > Manage

Hi, you can do that from Project settings > Types

Thanks for the context @Katrin Erhardt - you are correct for now you can't edit the name of that type - it's something we need to improve.