Tanguy Crusson Atlassian Team

Hi everyone, quick update: we've been testing this feature with lighthouse customers and it's gone really well so far: all except one managed to do what they set out to accomplish with it, and in some cases a lot more. You'll soon be able to try it as well. On that note: slight change of plan: we looked for a way to make…

Yep - 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

Hi @Lisa McCann you should see "insights", "number of insights", and "impact" could you please share what you're seeing?

Hi @Lisa McCann here's a video for how we do this in the team building Jira Product Discovery (link to the part where I talk about this): https://youtu.be/6P7HBBQyQ5U?feature=shared&t=1035 We've also tried to describe it in this product discovery handbook. Hope that helps.

Hi @Sonia Bramwell , at Atlassian we do use Atlas for that Basically when we work on something bigg-ish, we create a project in Atlas. People can subscribe to this project. Every week we send a short (280 character) update about the project with a status (on track, off track, at risk) for a target date (day, month, or…

Hi, you can find what we support today here in the product discovery handbook. That and the Chrome extension. We also have an API and an example for using it here.

Hi, I think this may be something you can solve with this upcoming feature (part of the premium plan)

Hi @Lisa McCann it is on the roadmap but I'm afraid not on the short term one still...

If you create a field of type "select" or "multi-select" you can then click on this icon:

Hi @Mohammad it's a current limitation of published views but something we have on the roadmap. Currently the only workaround would be to embed the view in a Confluence page and make the project open so any contributor in your site can see it. 

Hi @DuBose Griffin , * 1. you can't group by a date field yet - in our case we use a select field for "time horizon". Some teams use automation to keep a date field in sync with that. Not ideal, we'll have to make this better. * I think you saw a video for an upcoming feature (idea hierarchy, see details here). It's coming…

Hi @Faye Adams You are correct that's a current limitation of the tool - we've optimized for the jobs of prioritization and roadmapping, not yet for feedback management. The existing "insights" feature helps with collecting data points for specific ideas. (and that's how most companies use it). It's something for which…

Indeed it's not possible today, but on the roadmap we have the ability to use JQL to filter ideas in views. Which means you could configure a view that filters based on "creator = currentUser()". Only 1 view, same URL, and it would work for any number of users. Today you can't do it, but in the future it will be possible. 

Thanks for the feedback @xhammer - indeed it's not possible today, most customers who do this configure a hierarchy above epics (but it's only available in Jira Premium), e.g. to configure "initiatives" 

Hi @David - it's not yet possible today, but thanks for the feedback. We'll look at it when we iterate on that feature next 👍

Hi, yes, from the FAQ: How can we share a roadmap with internal stakeholders and customers? There are two options to share roadmaps in Jira Product Discovery: * You can invite internal stakeholders as contributors in the project. They will need a Jira user account, but as long as these accounts are only given access to…

Hi @Štefan Doležal we do have this on the roadmap but it's not supported yet

hi @Olivier CANU , there are a few examples for how to use automation with linked delivery tickets in the FAQ: Demo: project automation in Jira Product Discovery

You could export the insights using the API. there's an example here: https://github.com/Jira-Product-Discovery-Integrations/polaris-forge-ref-app/tree/master/get-insights-example

Note: it only works for the target date today, not the start date

Hi @Jeff Kukesh , you can actually set this up in the date field in Jira Product Discovery. Open the field configuration and select "Auto-fill date", then choose "Atlas target date" That way you can have a single source of truth for the date

Yep, that's it! In this case we used 2 fields. * a select field for "stage" (wonder/explore/make/impact) * a select field we use for "plan" (free/standard/premium/tbd)

@Erki Tammik thank you, that's great feedback. I passed it on to the team looking after admin features. 

Thank you @Tatiana Torset. I assume you mention Boulders, rocks and pebbles as we've defined them in this handbook? Here's a Loom where I describe how that works for us.

@Carlos Seguín Lozano In true Jira fashion different teams do it in different ways 🙂 In the JPD team we do a few things: * We have a public roadmap here (it's a public JPD view). We created it in a separate project to curate things differently. Honestly it's been fine to have 2 places: things don't tend to change very fast…

@Shelly Kitchen We're giving early access to the first version to 10 customers next week (already selected). When we've validated that it works for them we'll extend the invitation to the people who commented on this post. 

Hi @Kate - you are right, today JPD only works with #1. But #2 is a totally valid use case. Anything that gets good conversations going for what the priorities should be is fair game. It's not currently possible natively, exactly like that, though. We do have an idea we use to track improvements to the voting feature -…

@James Conway when we ship a feature we typically create an "improvements" idea, where we keep collecting insights - typically feedback from customers on how to improve it, gaps, usability issues, etc. Every once in a while we'll pick one of those, we'll allocate a budget (e.g. one team for X weeks) to iterate on the…

Okay @Matt Hudson I wasn't able to reproduce this 🤔 I think you're going to have to raise a support ticket so we can investigate (you can raise it directly from the JPD project > give feedback > select the option to get help from the support team

Hi everyone, we hear you! We've started working on this: copy project. And we're planning to look at more comprehensive project controls after that.