Tanguy Crusson Atlassian Team

Thank you @Nick Haller ! I've added this to the FAQ

Hi Susanna, we do have a feature in the upcoming Premium plan to have view-level permissions. In the standard edition what you can do is publish a view and decide who can access it. And people can only see what you've configured in the view. (try the "Publish" button top right of any view)

Hi Luis, you can do that by just copying and pasting a link to a view in a Confluence page. What I recommend you do is to create a view with your roadmap, then publish it, then copy the link to the published view and paste it in the Confluence page. 

Hi, yes you can do that by using "Insights - Impact" in a formula (weighted score or roll-up):

@Bill Sheboy it's going to be saved as issue links

Thanks for the feedback everyone. TLDR: we're not thinking of showing deep hierarchies from goals to work in JPD. However we're going to integrate this with Jira Plans so you can do that. E.g. in JPD you can have opportunities, solutions, experiments, editions, iterations. That's a graph of product objects. You ladder up…

Hi Glenn, not today. That's something that Confluence does and we use the same text editor so I'm sure it should be doable. Let me bring this up with the team. 

Hi @Andrew Lintag , I just checked and you're right! Only creators can export. Let me discuss with the team to see if we could give it to contributors (it does seem to make sense)

Hi @matthew.hockensmith it is not possible to do this today.

Hi everyone, it's been a while since the last update on this topic. Good news: we have started working on this. As a first step, we're implementing the concept of "issue type", and "relationships" between these issue types, as you can see in this Loom: https://www.loom.com/share/1d360838826842d396ff57d8048dec59 From there,…

Hi everyone, it's been a while since the last update on this topic. Good news: we have started working on this. As a first step, we're implementing the concept of "issue type", and "relationships" between these issue types, as you can see in this Loom: https://www.loom.com/share/1d360838826842d396ff57d8048dec59 From there,…

Thank you @Glenn A - we're currently looking at how to improve idea creation workflows so this is timely

Okay, in that case unfortunately you'll need to duplicate these ideas, one in each project. You can link them together directly, or have a project that lists all the cross-product ideas, and you link those to each product-specific idea. Not ideal I know, but Jira issues can really only belong to one project. 

@Jaime Matus do you manage these products in a single Jira Product Discovery project or multiple projects? 

Hi Mikko, if they are in your site then they have access to a bunch of things by default. For JPD, the way to control that is to make projects private, and give access to individual users or user groups that you define. If you make the projects open or limited, then anyone on the site with Jira access will be able to open…

Hi @Shafi G , I don't think you're in the right group for this question. Maybe try this one? https://community.atlassian.com/t5/Jira/ct-p/jira

@Glenn A For this purpose we usually recommend you give everyone "contributor" access to the project: all they'll see is the top-level "Create" button. That's typically in the use case where you want to let people from across the company to create ideas (leadership, stakeholders, etc.). If you want to make sure every…

Hi @Renee Bonnett the "implement" issue link type is reserved by Jira Product Discovery, specifically for that use case. I recommend you change the issue link type you use for other workflows, as we may make changes in the future that would have negative consequences to those workflows. 

HI @caio_santos , the templates should be shared 🤔 Are the other team members using the same Jira Product Discovery project? These templates are saved in the project

@Mike Chien for this use case you need to create a select field with multiple options (e.g. S, M, L, XL) and then you can give weights to each option. If it's a select field (not a multi-select) then you can only select one. 

Yep, 100% agree - for this today we recommend you create a new field for each new round. That way you reset, but you also keep the history over time. 

Hi, that description isn't correct - you can only search goals in JPD and associate them with ideas, but not create them (you need to create them in Atlas) Details here: https://community.atlassian.com/t5/Jira-Product-Discovery-articles/Goals-and-projects-integration-ex-Atlas-ready-for-early-testers/ba-p/2195274

Hi @David Beacham , you can't do it exactly like that today, but what we've seen some teams do is something like this with the field description. A bit less discoverable than being able to add a description to the field value, but that part doesn't exist yet (in the screenshot below I used emojis to represent yellow dots)

anyone who has perms to view the insights can pull them

Hi @Jeny Stoeva there are examples for how to use the (still experimental) API for insights here: https://github.com/Jira-Product-Discovery-Integrations/polaris-forge-ref-app

@Florian Schmidt it is there 👍

OK everyone the images in the handbook were fixed, an issue with the editing tool for the last export had thrown all images off for some reason... Thanks a ton for reporting this @Tim Balzer !

@Brandon Bell you could give them a million votes or something. The logic for the feature is to give people a budget to allocate to ideas to get them to think about relative priorities and constraints. At Atlassian we call it the "$10 game": if you had $10, how would you spend them? e.g. $5 on this idea because of…

Hi everyone, it looks like we borked something up when generating the PDF version of this handbook and most of the images in there are wrong... Thank you @Tim Balzer for bringing this to our attention! It's a public holiday in the US today but we'll jump on it to fix it tomorrow. In the meantime, you can access an earlier…

Thanks @Tim Balzer , you're right! We'll fix that 🙏