Rohan Swami Atlassian Team

@Bill Sheboy is exactly right here. @PeterE we're thinking about introducing date syncing across Jira Product Discovery and Jira Software in the future, would you like to speak to us about your use case? https://calendly.com/rswami-atlassian/customer-calls

Hi @Steve @Christina Kogiou Contributors get their permissions for all views within the project. A few options that might help: 1. Creating folders for your views so that Contributors know which views are intended for them. 2. Create a separate project for work you don't want to be visible.

Hi @Sabina Alistar 1. For now you can not see the delivery tickets themselves on the timeline. When you create the timeline you select which date fields you want to use, note that these fields are from Jira Product Discovery, not the dates from your linked delivery tickets in Jira Software. 2. This is up to you. We find…

@Erki Tammik for now the ideas aren't editable, we'll continue to improve this feature over time.

Hi @Karthiga Sethuraj please continue this in the support ticket you have open with us and we'll be able to give you more targeted help.

@James Fama remove the site admin group from access, then add yourself for access.

Hi Karthiga, CSV import will keep formatting as long as you keep the same markup language that we use (\* bold text \*, \- strikethrough \-, that kind of thing). See the examples below for markup guidance. To create a Kanban board: Create a view > Create a new board > For columns, select Status.

Hi @James Fama Is this right? Is it necessary to perform First Steps & Second Steps? Yes Administrator has Creator access plus admin access to the project. So if I added a user with Administrator role she automatically she has Creator access right? Or do I need to add Administrator and Creator access? Within a project, the…

@KB To add users with Jira access as contributors: In each project, add the users with the project role as Contributor. To add users without Jira access as contributors: Add the users to the jira-product-discovery-contributors, then in each project add the users with the project role as contributor. If you're still having…

Hi Abby, we announce all new features here in the Community, keep an eye on these pages.

Hi @Alexandre Krammel in case you haven't seen it, we have a post on how best to do this with the current capabilities of the product. See the section titled "Can we create different issue types and their relationships? (e.g. parent/child or opportunity/solution)" on this page. Rest assured this is in our plans for the…

Hi @KB , @Gary Spross is exactly right here. Add users to the group in your screenshot, then you'll need to add those users as contributors to the project from project settings.

Hi @Sebastian Pechhold please raise a support ticket with us at support.atlassian.com and we'll investigate

1) Text fields are capped at 255 characters and don't support multi-line but you can insert long form content into the description of the idea. Can you help me understand why you need this? 2) Not at the moment but we are working on this! 3) Not at the moment. 4) Yes you can do this!

@Simone Longoni you can also go through support.atlassian.com 

Hi @Mallory West you'll need to export from Jira Software to a CSV then import to Jira Product Discovery to do this.

Thanks for the suggestion @Sebastian Pechhold ! We'll keep this in mind.

Hi @Sebastian Pechhold do you have filters in this view? We can take a look at your view if you raise a support ticket at support.atlassian.com 

@Karthiga Sethuraj if @Jacques' suggestion doesn't work for you please create a support ticket for us: In the bottom left of JPD select Give feedback then Get help from the support team.

Hi @Simone Longoni This depends on the view type you've created. For timeline views, select the date field you want to use for filtering as per below: For the board and list view, add a filter for your desired timeframe. If you're having difficulty, please create a support ticket via the 'Give feedback' button on the…

Hi @Robert Barbosa while we don't have a public roadmap we regularly share details on upcoming features in this Community group, you're in the right place to get the news first!

Happy to help! https://calendly.com/rswami-atlassian/customer-calls

@Kyren Cabellon it really depends on how you want the field to be used! We've built this in an abstract way so that it can be extended to a wide variety of use cases for example: feedback (heart, fire),voting (thumbs up/down), metric themes (cash for revenue, heart for customer love).

@Len Bergman if you're still having issues getting in to your JPD project please ping me at rswami@atlassian.com

Hi Ryan. We've also now released a Reactions field type which can function more like a permanent field for voting, it has the additional flexibility of allowing your team to express themselves in different ways (eg. pick a heart emoji if you think this will delight customers, a cash emoji if it will improve revenue). Bear…

Hi @sureshr - @Gary Spross is right. We'll be addressing this in the future.

thanks @Alex Hoogendoorn i've shared this bug with the team

Thanks for the suggestion @Matt Jones ! We'll keep it in mind

Hi @Sarah Green we weren't able to reach out to everyone in that study, hopefully we can find a timeslot today (Friday)? https://calendly.com/rswami-atlassian/customer-calls

@Paolo Pastorino I can't promise a timeframe at this point unfortunately. We'll review our prioritisation as we get more feedback from customers about the feature, we only just released it.