Tanguy Crusson Atlassian Team

@Solenne CLEMENT Update: I spoke with the engineers and there are a few corner cases that don't work well yet. The following cases don't work: * A user is a Jira administrator: it's not working currently to add them to the contributor group * And in some cases things didn't sync properly in the past They suggested you try…

HI @Solenne CLEMENT , that's weird indeed. Can you please check that the contributor group is configured with the contributor product access for JPD? 

Hi @Karina Paula-Freimane you can't yet create a custom project template but we have a team working on it: 

Hi @Karina Paula-Freimane you can't yet create custom Discovery project templates but we have one team currently working on something for this:

Hi @Victoria Alexander , it's not yet possible today but something we have on the cards for later. 

Ok we've tried it and we think we know what the problem is: it's a bug in how we show the new votes immediately after the people voted (without having to refresh the page). In the short term what you can do is refresh your page --> that will show the people's names. We'll fix it so the name appears at all times. 

Hi @Weronika Siatkowska does this happen for every user? 

Hi @Daniel de Cordoba Gil , based on this information we were not able to reproduce the problem. The only way we can investigate is if you give us temporary access to your site via a support ticket. If you're game, here's how to do it * From JPD: left sidebar > give feedback * Choose "get help from the support team" *…

By the way, let's say someone uses 10 emojis to vote - would you still like to sort by the number of reactions, or by the distinct number of different people who reacted? Hmm, actually, it's kind of a rethorical question since the only one we can implement easily is the former (number of reactions). But people can still…

Hi @Yiling Baldez , you're right, it's an oversight (currently it looks like it's sorting based on the number of distinct emojis, vs the number of reactions). We'll fix that! Thanks for reporting this. 

HI @Luka Hummel - codefortynine : using the issue link (is data point for / is idea for) does not suffice to create insights - you do need to create the insights either via the UI or the API for it to work. It's something we plan to add later (that the insight gets created if you use the issue link. You have 2 options: *…

Hi @Stephen Newman that's a current limitation of the product: formulas are only calculated client-side and not saved in the backend - so they are not available for dashboards, JQL, automation rules, etc. We'll fix this, but it's not going to be in the short term 

Hi @N Lalitkumar you can create an insight on the target idea and put a link to the other idea as the insight link. That's the only way I can think of to do what you described.

Alternatively, if you could share a screen recording (e.g. Loom) to tcrusson@atlassian.com that shows the view configuration (group by, filter, sort, fields) and the published view, that would work too

Hi @Christian Amaya , could you please raise a support ticket so we can investigate directly in your site? It's going to ask you for permissions to do so While in Jira Product Discovery left sidebar > Give feedback > Get help from the support team Thank you

OK I confirmed with the team and everything should be back to normal now @Owen Scott . Can you please confirm?

Hi, I believe we've had an incident related to app authentication and this looks related - I'll confirm with the team tomorrow. 

Hi @Wendy Grapentine , it's not possible to find these issues via search (the resolved ones), however you can copy the link/URL for the issue in Jira, and paste it in the search box in the delivery panel in the idea, and that should work just fine. Let me know if that's not working for you!

Hi Glenn, you can't do it like that today: the formatting applies (or not) purely based on this date field (not a combination of field values). You could turn off formatting altogether though for that field? We've been discussing other ways to colour ideas based on field values: e.g. make it so you can apply it to specific…

Hi, this is where we talk about this: https://community.atlassian.com/t5/Jira-Product-Discovery-articles/Early-Access-Program-new-integration-with-Jira-Plans-ex-Advanced/ba-p/2743110 the integration is still in early access but not for long - we'll turn it on for everyone soon.

Hi @Florence BLEUSE was your question about Jira Product Discovery (this group) or the rest of Jira? If the latter, then the best group to ask is that one: https://community.atlassian.com/t5/Jira/ct-p/jira

Have a look at this: https://community.atlassian.com/t5/Jira-Product-Discovery-articles/Goals-and-projects-integration-ex-Atlas-ready-for-early-testers/ba-p/2195274 One way we use it ourselves is: * Goals connected to Ideas * Ideas connected to Epics (for planning and tracking the work) * Ideas connected to Projects (for…

@Ivan Muccini Project Settings > Features > Atlas integration You can watch the Loom in this post to see a demo for how to use it.

Hi @Viktor Chuiko , this is exactly what we've built Atlas for, and why we integrated JPD with it. I can't really think of a solution that does what you describe without Atlas unfortunately. Thanks for the feedback. 

EXCEPT when you use global fields. And then you can move ideas between projects and the values are retained. https://community.atlassian.com/t5/Jira-Product-Discovery-articles/Product-Update-Global-fields-amp-Fields-management-page/ba-p/2699796

Hi @Michael Mackuliak - the definition of fields is unique to each project by default. Meaning a field named "A" in one project is not the same as a field named "A" in another project. That's why the values are not retained when you move the idea between projects (if you move the idea back to the source project you'll see…

Done.

Thanks @Mart Postma - we do plan to make the fields you see here for each idea configurable - it's on the roadmap.

Hi @Sébastien LIEVAIN , I've added a couple of videos to the FAQ to explain how to reproduce this configuration: How can we create a roadmap at 2 levels? (one with a list of themes, one for each theme?) - sort of like a hierarchy During this webinar we've demonstrated how the JPD team uses a roadmap at 2 levels: one for…

Hi @Jodi Jones you can invite them to the project as "contributors". They will need an Atlassian account (which is free) and won't need a Jira license. They won't be able to access the other parts of Jira. Then you create a view with the list of ideas you'd like their input on, and you add fields to let them comment and…