Tanguy Crusson Atlassian Team

hi @David Spire - we didn't prioritize that last bit up until now, but let me see if we can get to it soon. Edit: someone is looking into it now.

Thanks @[deleted] ! Where were you looking for it @Brent Johnson ? We keep adding this menu in more places as this question keeps coming up :) 

@David Spire the issue is fixed. It applies a value automatically for Assignee, people fields, labels Not for status yet though - but at least it doesn't throw an error. For status it will ask you to specify a value. We'll follow up later to make sure this one is auto-applied too. 

No worries @David Spire , we're working on it and I'll let you know when it's fixed (shouldn't take long)

@David Spire thanks for that! it looks like you found a bug with 2 field types: user fields, and label fields. We're on it.

Update: we've improved it so it now works when you have more than 50 child issues in the tree. Something faced by a few people

Hi Zuzana, Where would you like to type the Jira issue key? This is how Jira Product Discovery works with Jira issues today for prioritization: Video demo

Thanks for the feedback Zuzana - we'll look into it.

Hi Zuzana, the way this works is: - if you make a project private then only the people who have been explicitly added to the project can access it. - If you make it limited then anyone with access to the Jira site can at least view ideas and comment (and you can grant people more access). - If you make it open then anyone…

@Colin Goudie you got it! And then it got to the point where we were like... Fuck it, let's do it (pardon my French) (pun intended)

Hi David, Thanks for this feedback. We already have this on the roadmap - so you can track things like "initiatives", "problems", "solutions", "opportunities" and their relationship. What types of issues are you interested in, and how do they differ? Thanks, Tanguy

Hi @Martyn Arbon , this is not currently possible - the fields you add to a Jira Product Discovery projects are just local to the project (not to bore you with the details, but that's because the product was built on top of Jira NextGen). Eventually it will be possible, but not yet. 

Actually it looks like I spoke too fast - the problem should be fixed now. Let us know otherwise @Josh Kahle !

Hi @Josh Kahle , yes, we do have a bug for this that we discovered late last week. We have fixed it and it's pending release to production. 

@elizabeth_jones my apologies I forgot to send an update - we've been battling with this a bit, and the changes we made for advanced roadmaps created issues for Jira sites that weren't using it - so we had to disable the feature to fix this. We've now found a fix and it's getting rolled out before we turn it on again. We…

@Allan Maxwell it's already live

Thanks for that @elizabeth_jones - I completely understand. It's already in our roadmap but I don't exactly know when we'll start on this yet. We'd love to chat with you when we get to it though if that's OK! In the meantime, here's our roadmap as it stands at the moment:…

@Erin Mihalik thank you and sorry for the late response - we're looking into it.

We've now turned this on for everyone 

Okay, everyone's got access to it now!

@Dave Hennessy @Lukas Karrer It's on - you can start using it. if you face any issue: please let us know! The only fields that aren't going to show there right now are: * Delivery progress * Delivery status But we're working on them at the moment.

@Dave Hennessy @Lukas Karrer we had to fix something re: product analytics for this feature, which means that I'll probably give you access tomorrow. Stay tuned!

Hi @Curt Holley , that is correct - what we've added is viewing the hierarchy and rolling up the progress. Before that it would just show the initiative ticket.

@Dave Hennessy done.

It's already possible today, if I started using the product now I'd only make one. There are a few things we want to do to make it easier (i.e. the "idea hierarchy and nesting" idea above). In all honesty I have no idea when that's going to land as we're still exploring concepts there - and we're planning to launch the…

For the Jira Product Discovery team, we currently use 2 projects. We link the ideas between the 2 projects and copy data points over, our goal is to make it so it's easier than today to do in a single project: Project 1: purely used to keep track of feature requests. On this one the prioritization views are based on 2…

@Curt Holley @K.Q. Dreger @Erin Mihalik @Nans Thomas we've turned it on for you!

Hi @[deleted] - we're most likely going to do the latter: letting anonymous users view some level of details. What would you like to show? As for commenting: this is actually not possible in - for any action that is more than viewing we need to have an identity for the user performing the action. With that constraint in…

@[deleted] It's now fixed! Exporting a PNG works when you use group by

Great question. We've seen teams using both approaches: one project to rule them all, multiple projects. And we've seen both work. At this stage we don't have a definitive guide/recommendation for this - it's actually part of what we're learning in this alpha. My 2 cents on this so far: * We've designed this to work well…