Tanguy Crusson Atlassian Team

Thanks for sharing @Annie Ioceva _Nemetschek Bulgaria_ ! In the JPD team we do the same as you do: collaborate in whiteboards (Confluence Whiteboards in our case) to workshop the product strategy - then JPD for driving things forward. Here's an example of whiteboard (after we've cleaned it up) for how we think of…

Yep, the problem is we call 2 different things with the same name, that's confusing... But basically: * Being a creator on the site means you have product access = a product license * Then, in each project, you can be added with a specific project role. By default, projects have 3 roles: project admin, creator,…

Hi @Andrew Bryk , I can't really think of a way to do this today short of creating global automation rules that updates number fields (which would be cumbersome)

mmh, I wonder if it's an issue with timezones. Let me check with the team. Thanks for raising this!

Hi @Laura Skosnik you cannot restrict the picker to only precise dates. Thanks for the feedback. 

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

Thanks @Michael Roberts @Matt Jones @timothy.lelek - that makes complete sense. We're working with the Jira Plans team to figure out how to address this 🙏

It's hard to make this one discoverable! We've tried a few different ways. So in your case, I'd recommend to : * create a list view * add the global field to that view * group by the project field * and then in a few clicks you can set the field value for all ideas. 

@Simone Longoni @Thierry BLOCH Funny you should ask: just this morning we had a design review about a tool to help you in that transition. We haven't started building it yet. Today you'll need to create and configure the new field, then update ideas that use this field to have the right value - which you can do via…

Hi everyone, We've given early access to about 100 customers who asked on this post up until a few days ago (if we could locate your site based on the URL you provided). If you have access you should see a notification about it in JPD when you open an idea. To give us feedback about the integration: you can just add a…

Thanks for the feedback @Eduardo Calvillo - in the meantime we'll rename "Atlas project" to "Atlas project target date" to remove confusion. Thanks for reporting this. 

@Eduardo Calvillo @Kostia That's because you can only use the Atlas project target date for this feature today - not the Atlas project start date. We'll add this option at some point. 

Cool, thanks for the feedback @William Perkins . You can associate ideas together by linking them (then the link is visible on both ideas). We're currently working on a solution that makes all of this easier and more native.

Hi @gabriel_moraes , at this stage the only way to do this beyond comments is to add users as contributors to the project. We're going to do a fe things to make this better: * currently we're working on "view permissions" so you can restrict access to specific views in a project to specific people or groups (that way you…

Thanks for the feedback @Patrice Cantalupo 

Thank you for the feedback @katie.steyn 

Hi @PATRICIA MURPHY the only way I can think of to do this is to create custom project roles in Project settings > Access that exclude the ability to delete ideas, and to give these project roles to everyone you add to the projects as creators. That will work if project access is set to "Private" or "Limited" (if it's set…

Hi @Robby Keefer : @Hermance NDounga (our resident expert for this) is currently away but will reply as soon as she's back.

Hi @Wendy maple , can you please confirm that you've added the email address for this stakeholder in the configuration of the publish dialog and you can see them in the list of people with access? 

Note: we're currently working on a feature that will eventually help you do things like this:

Hi Kevin, Today we use JPD ourselves (in the team creating JPD) in both ways: sometimes ideas that encapsulate the entire effort are on views, sometimes we split ideas in multiple ones (and link them together) when it makes sense from a product perspective. On that topic, there is this question in the FAQ that may be…

Hi George, you have 2 ways to think about it: * You could create a single JPD project for all products, and create different sections with views for different teams and products. That way an idea can appear in different products and teams views. We have customers who have 250 people working in the same project. If it's set…

Hi Katie, we recently changed something there - can you please confirm if that's what you're seeing? https://www.loom.com/share/ebca2c507c3743678ee5d138012035da

Hi @James Conway , what @Nick Haller said, but also: yes, it's on the roadmap. In fact we landed on a solution that's looking promising and the team met to kick this off, starting with a technical spike. We'll post in this community when we have something in early access (but we're still a while away from being able to do…

Edit: it's done - if you refresh your screen you should see this option now @Jess Wong 

@Jess Wong We found what your issue is (thank you for reporting it!). There's something we forgot to turn on when rolling this out to everyone. We'll fix that soon.

Hi @Alaina Gardner , based on your questions I'd like to try something: we're working on a handbook to explain the ways of working that come with Jira Product Discovery and how to use the product. I'd love your feedback on it. I think it answers the questions you asked there, but if that's not the case then we can iterate…

Hi there, not yet but it's something we're working on. It will be a feature part of the JPD Premium plan. You can join the waitlist to get early access here: https://www.atlassian.com/software/jira/product-discovery/premium 

@John McDonald that's an oversight on our part: the Atlas project field is not yet supported in published views, so you shouldn't have been able to publish this view in the first place. We'll start by fixing that. We'll add support for Atlas project fields in a subsequent change. Thank you for reporting this!

Hi @jack_saxton thanks for the feedback - we'll pass it on to the team working on "Smart Links" (when you paste a link - it transforms into a card or embed in any Atlassian product text box).