Rohan Swami Atlassian Team

@Hannah Garvin could you book a meeting in with me and we'll work through it together? https://calendly.com/rswami-atlassian/customer-calls

@Mary Kaczmarek We're at a very early stage with this product (it's still free to use!) so we may very well tackle these problems in the future. There's a tonne of features we want to bring to customers and it's a tough challenge prioritising between them, as every Product Manager knows! We don't set guidelines on how our…

Hi @Gabriel Buck most customers are using the voting feature as part of a collaboration session. For example, let's vote for our top 3 out of these 10 ideas. It's a point-in-time activity. So I'd also recommend @Radosław Bielak 's suggestion to create a field name for the session.

Hi Abby, we might be talking about 2 different things here. One functionality is having related ideas and parent/child ideas - this is on our roadmap. You could probably use this capability alongside the existing Assignee field to do some basic task tracking for ideas. Building out specific task tracking functionality on…

Hi Mary, these fields should be editable by an admin. Could you please test with an admin and let me know if that works for you?

No need to - I'm glad you got it working!

@Nulat Danur Wendo we don't have a Zoho CRM integration at the moment. If we were to introduce it, how would you like it to work?

Thanks for your feature suggestion @Christina Kogiou , we'll keep this in mind when we make improvements in this area.

Hi @Mary Kaczmarek , Currently Jira Product Discovery is focused on the Discovery side of the problem, we don't really have task tracking features in their beyond the basic ones previously mentioned by @Abby Kiesling and @Ivor (Assignee field for an idea, add tasks in the description field). To track the work of…

Hi Hannah, here's some extra info from one of our engineers: We use OAuth authorization (3LO) with these scopes a.Access the identity URL service (id, profile, email, address, phone) b. Access unique user identifiers (openid) c. Manage user data via APIs (api) d. Perform requests at any time (refresh_token, offline_access)…

Hi @CC - @Ivor is exactly right here. Thanks Ivor!

@Hari here's a guide: https://confluence.atlassian.com/jirakb/restrict-field-editing-to-specific-user-1189510558.html

I'm so sorry I forgot to include the link! https://community.atlassian.com/t5/Jira-Product-Discovery-articles/Product-demo-Automation-for-Delivery/ba-p/2057152

@Hannah Garvin there are a few Automation demos here let me know if you can solve your use case with them.

Makes total sense - thanks for that context @Gary Spross 

Thank you very much for that context, Hannah. For now I would suggest that you set up Automation rules to copy across data from Jira Product Discovery to linked Jira Software issues. The Delivery tab is V1 of our JPD/JSW integration, we'll keep making improvements to it over time but we need to make some tough…

@Hari you can restrict updating certain fields in Jira Software, but it's not supported in Jira Product Discovery at the moment.

@Gary Spross what sort of metrics are you looking at from JPD?

@Martin can you please create a support request so that we can look into debugging? Select 'Give feedback' at the bottom of the left nav in Jira Product Discovery. In your support request please include details of the rule that you are trying to implement.

Thanks so much for that context, Florian. It's really helpful for us as we try and prioritise where to improve the product. I'm sure we'll be in touch in the future when we get around to addressing this area of the product.

Thanks for sharing that context @CC 

Hi Hannah, Thanks for your feedback here. There isn't a bug here, we deliberately chose not to pull the Overview into Jira Software boards because customers wanted to display different information in the discovery context of Jira Product Discovery vs the delivery context of Jira Software. What's the benefit you'll get from…

@Ivor is correct, @Hari. This isn't on our roadmap at the moment. However, we are introducing creator and contributor roles, where contributors are restricted to certain interactions like viewing, commenting and voting. Contributors won't be able to update field values. Would that solve for your use case?

Thanks @Jens Schumacher - Released_so ! That's correct. @Jeny Stoeva Another way is to look for 'Give Feedback' at the bottom of your left panel in Jira Product Discovery.

@Florian Royer @Curt Holley @Gary Spross For now, it's not on our roadmap to have Company-managed projects. As you've pointed out, the flexibility of Team-managed projects is hugely beneficial to our users which is why we've started with Team-managed initially. That said, we are aiming to support projects with shared…

Thanks for sharing your feature request, we'll keep this in mind as we improve the timeline view over time. @CC What are the time increments you'd like to see on the timeline? @Ian Sperry Who's the audience for the date milestone? What sort of information do you want to display here?

Hi all, as you've identified the extra bits on the end of the URL dictate the view that the idea will be opened in. We'll look to improve the URLs at the some point, but it's not on our roadmap for now. Personally, I agree with you that when sharing a link I want to take someone to see the idea and not the view. But this…

Hi folks, As Tanguy said already, we're making progress on sharing. We're also exploring eliciting input from your stakeholders for your prioritisation. If you'd like to discuss your use case and how we might solve for it, please book time in with me on Calendly here. 

Ah gotcha - Generally our customers create these milestones in Jira Software which has more flexibility for breaking down the work and supports creating releases. Thanks for sharing your use case!

hi @Ahmed Salem thanks for sharing your feedback, we'll keep this in mind as we take the product forward. Which 'jobs' are you doing in Jira Product Discovery vs Jira Software? Jira Software handles detailed planning and project management very well, so I'm curious to understand why you are choosing to do that in Jira…