Tanguy Crusson Atlassian Team

@Seth Mason we don't generally comment on timelines for the delivery of features. Not because we want to hide anything but because we genuinely don't know what will happen that can make us have to change plans mid-flight 😅 In the meantime, what we've seen teams do is create a corresponding "Goal" field in JPD with values…

Hi @Seth Mason , FYI where we're going with this is we're going to integrate with Atlas , which covers goals/sub-goals which you can use as OKRs - and report on progress for those. This means that you'll be able to add an "Atlas Goals" field to a view and use those to set goals to ideas, and visualize which ideas ladder up…

It's awesome to have you onboard Hermance, welcome to the team!!! 👏👏👏

Thanks @Nate Dame , by the way this is how it works for boards today if you generate columns based on the values of a multi-select field: * You can add the same idea to multiple columns (multiple values for the field) * if you drag and drop, then it acts as a "move": it removes the first value and sets the second This…

I haven't tested that but I don't think that would work - unless Project Automation gives you a way to map the content of the form to fields in Jira Product Discovery. I've asked the team working on Forms to weigh in on this. 

Edit: that'll be next week!

hi @brent_johnson , this is what I would try to do: https://www.loom.com/share/c3365662388e4dcaab8b708b130ba7b8

I made a mistake in the initial reply to state that prioritization should be time-boxed - I meant that we think (rightly or wrongly) that voting is an activity that is better used in a time-boxed manner, for a specific context/goal. I edited the reply. 

Hi @adams.laborde , what @Bill Sheboy explained is what we tried to do here, where voting is a point in time activity, not an ongoing activity - that comes from a belief that prioritization should not be a crowdsourced activity, so voting is instead something we think PMs should use use to gather feedback in a time-boxed…

Hi Omer, sorry about the delay, we'll get to your question tomorrow!

Hi Brent, sorry we couldn't get to your question today, but we'll do tomorrow!

@Jeremy Tang we just used a landing page that didn't even contain any screenshots, just a "letter to product managers" and a way to add your email to join a waitlist. We then advertised it in a newsletter that goes to Jira users. I couldn't find the actual letter we used, but this is what I had jotted down back then as a…

Hi @Seth Mason , that's a limitation of the beta currently: we don't really support moving ideas between projects yet. E.g. if you move an idea to another discovery project you'll lose the connection to insights. It's something we definitely plan to support on our way to GA.

Thanks @Jonathan Hau ! Yes to this: basically you can create a new field (type: Vote) and add it to the view people use to vote (or a new view). The old field will still be here so you can see previous responses. You can also create a view with both fields to see how ideas are trending, etc.

@Riku.Kristersson done. @Karl Mentzer I just checked and it was already on for you!

@Jeremy Tang Thanks! I believe most of these recipes can work for startups and scale-ups (when launching new things). The main difference would be that you probably want to experiment with distribution strategies super early to validate there's demand (even if you don't give people product access) - because once you decide…

Thanks for letting us know @Jeremy West !

Hi @Seth Mason , it is not possible today. What's the reason you need the shorter version today? Thanks!

Hi @sharon.prajzner , it's one of the shortcuts we took to get to beta - we need to add the ability to add watchers, etc. but haven't done so yet. We definitely will though!

The issue is now fixed, thank you!

What @Chris Hall said! Also, if they or their Jira admin want to see what the product is about before adding it to their site, they can see the product tour here: https://www.atlassian.com/product-discovery ; and then sign-up from there. 

OK thank you - we're investigating!

Another potential issue is if you have a list which is sorted by a field (can't re-rank ideas when that's the case)

Hi @dangbingyao , are you trying to do this in a list where you have a "group by"? If so it's a limitation we have currently but working on adding right now

There's something we need to do later which is to support the case when software projects have mandatory fields for new issues. In which case we could for example pop open the issue creation box - instead of just failing like it's doing currently

Hi @Florian Wahl, what we're using here in this menu to collect feedback for Jira Product Discovery is a Jira Service Management queue. That way we can receive, respond to and discuss feature requests there, and then decide what we add as insights to ideas in the Jira Product Discovery project - where we manage the…

Hi @Jeremy Gaudet Thank you for the feedback! It's a known issue and one we're currently working to fix. It will at least warn you when you navigate out when typing a comment or insight

Thank you @Omer Meshar you got it right! @Matt Lane basically: * you can configure "default fields" when opening an idea * you can configure "view fields" in the view's "fields" configuration (board, list, matrix) - what we show here is any field that is part of the view you just opened the idea from, if it's not already…

@Tomislav Tobijas this is something we plan to do eventually. For the moment you can use the Chrome extension to send snippets of a Confluence page to an idea, but you're right, it's doesn't make it a bi-directional link!

Hi @Seth Mason thanks! Yep we have a follow-up task on the "group by" to address that in list views. It already works in board views.