Tanguy Crusson Atlassian Team

Hi @James Doyle , it's high on the priority list but we have a number of things in flight now that will take a few months to land before we can get to it. However we're not going to build a "parent/child" solution that looks like the Jira Software one. It's going to optimize for things like "opportunity/solution" or…

Thanks @Kalina Lipinska ! I saw your feedback and was about to send you that. 

hahaha thanks @__ Jimi Wikman , your reply made my day

@__ Jimi Wikman 😂 We've put it on the short list. Just to give you some insider info on this as to why things like this aren't always easy: * We checked and this description it's not a Jira Product Discovery specific thing - it is something that's used across Jira, and it's not a rich text field. * Changing something for…

Thanks @__ Jimi Wikman , just let us know when the pull request is ready 😉 Yep, good point @brent_johnson - let us see what we can do there!

In what ways do you think it's better than the Jira roadmaps @Bill Sheboy ? Thanks!

@Bill Sheboy thanks. One thing that would help me is: what do you use this board for / what's your scenario? Same question for @Dave Perini actually!

HI @Aidan Depetro , it takes a bit of configuration to do but you can do it in Jira Product Discovery today. From the FAQ: Can we create different issue types and their relationships? (e.g. parent/child or opportunity/solution) Not yet, but it's on the roadmap. In the meantime you can use the flexible fields and views…

@Bill Sheboy boards based on date fields are pretty much useless today. We're actually in the middle of changing all this, starting with the introduction of a new type of date field: This one we'll build support for filtering for, and make it so board columns are actually usable 😊 For example: It's going to be delivered…

@Bill Sheboy that's correct, the way we designed this is so you can do things like "highlight high priority ideas everywhere", or "highlight all ideas that have been published in some form of public roadmap". We're thinking of revisiting "colours" across the app at some point, so that you can for example select a field to…

@Paul Newell we've just shipped what you suggested. Literally as-is. Thanks, you're now an honorary designer for Jira Product Discovery 😉

@James Cody you need to create a Jira Product Discovery project: Projects > Create project Product management > Product discovery

Thanks @Vincent Coval that's a great suggestion. You can already do this today actually using a bit of configuration: Demo: good and bad insights Does that help?

@David Nadri we plan to integrate Jira Product Discovery with Atlas Goals and Projects. Have a look at https://www.atlassian.com/software/atlas (that's what we use at Atlassian to manage our OKRs)

Short answer: a timeline view is coming soon, the team's actively working on it now. It's probably going to be a few weeks before we start sharing something about it. It's not going to be a Gantt chart though - not meant to be used for delivery planning, but for prioritization discussions and high level time-based…

Hahaha I can see someone's worked in a big company before 😅

@Nicole Downes new Atlassian products from Point A like Jira Product Discovery are not supported in sandbox environments. However you can create any number of new sites with the product to test it, it's free during beta. 

By the way @Radoslaw Cichocki {Deviniti} you should already be able to embed a read-only version of your views to a Confluence page by copying and pasting the link to each view into the page. Let us know if that's not working for you!

Thanks @Radoslaw Cichocki {Deviniti} that's super useful context

While it's in beta we haven't added it there, but you'll find an example here: https://github.com/Atlassian-integrations/polaris-forge-ref-app Look in "push-example"

@Matt Lane here's how I would do it: * Do what @Erin Mihalik suggested: add the "jira-software-users" group to the Administration -> User Management -> Product Access ->Jira Product Discovery * Make sure that your Jira Product Discovery projects are set up with "Limited" project access: Project Settings > Access > Project…

It's definitely on the list of things we plan to look at. For this particular scenario we're not completely sure how that could look like though. Some things are easy to grasp, e.g. someone commented on the view = send an email notification. What if an idea shows in the view and was filtered out before? What if someone…

@Christophe Promé you are right: when you add a Jira issue to an idea as an insight, the product creates an issue link between the too. But today just creating that issue link doesn't automatically create an insight. The only ways to create an insight from a JSM requests: * copy-paste manually the JSM ticket in the idea's…

@Dave Nicholson done

@nwatson yes, in Jira: - Filters - advanced issue search - search for the ideas you want to export - top right: Export > Export Excel CSV

@Nicolo Yes, we retired that implementation and have started another one. Initially it focuses on the internal use case (people from your company) and will eventually expand to people outside your company. 

@Omer Meshar nope, not yet - we're focusing on other things at the moment - cc @Catalin Bridinel 

Thanks everyone, I'll keep watching this post and next week I'll reach out individually to understand your context, share what we're thinking and get your feedback 🙏

Hi Gary, that means that "epics" in the "product ops" project have mandatory fields without default values - meaning: if you create an epic there are some fields you need to specify, and these fields don't have a default value. In this case Jira Product Discovery doesn't know what value to give to those fields and returns…

That's brilliant @Paul Newell , thanks! we'll see if we can add that in the near future