Rohan Swami Atlassian Team

@John Wagner you have great ears and audio equipment!

apologies for the slow response I've been sick for a few days. @Sam Hepworth we won't be supporting Start date from Team-managed projects anytime soon. It's not a system field under the hood like due date, which makes it a lot of effort for us to build a solution here. We've found that most customers who need this feature…

@Blake Falanga Shared fields and field values across Jira Product Discovery Projects is coming soon. There are more details in this post. Can you tell me more about your use case for wanting to have shared fields/values across Jira Product Discovery and Jira Software?

@Tate Zellner could you please share your site URL? The video in this post is still up to date on how the Atlas feature works.

@Sreenivasaraju P is exactly right! thanks

@Thiago Pinheiro thanks, I've recorded your feedback for our future reference.

Hi @Thiago Pinheiro thanks for your question. I'm curious about how you would like this to work. Would you like to link an idea to a version/release as an alternative to epics? For example if an idea has 2 releases, do you want the delivery progress bar you see for that idea to aggregate the delivery progress across those…

@John McDonald I've just tested and it's working as expected for me, the Atlas date is overwriting my date field in JPD. Could you share a screenshot of what you see in the config when you select Edit field?

@Christy Johnston you link an idea to an initiative the same way that you link an idea to an Epic. There are a few different ways you can do this: * To create a new initiative: In the Delivery tab of the idea select 'Create a delivery ticket' then select the Initiative issue type. See the screenshot below. * To link an…

@Christy Johnston My recommendation is that you link ideas to Initiatives, and the Initiative is the parent to Epics. Here's a Loom demo on using Jira Product Discovery with Jira Software, and the specific part about Advanced Roadmaps/Plans is at 7:35.

@Gilles Taillon the date used in JPD is based on your personal Jira settings for your timezone while the date coming from Jira Software is likely a 'system' date. Your Jira Settings can be found by selecting the Settings gear icon at the top right > Personal Jira Settings > Your timezone. We're aware of the bug and will…

@Blake Falanga could you please create a support ticket so that we can look into the issue for you? @Roeland Schoppers I recommend you use Automation to update the start/end dates based on the issue's sprint, here's a previous Community Post on setting this up. @Jeff Wasserman the date used in JPD is based on your personal…

@Julia Spanier could you please share your site URL? @Kate thanks for sharing your feedback, I've recorded for future prioritisation.

@Troy Moore thanks again for your time! Our PM team always takes the chance to speak to customers about their feedback and what they're struggling with to inform our roadmap. We synthesise the feedback, evaluate if there is a problem worth solving, see if it aligns with our strategy, explore solutions, and sometimes we get…

@Niki Kavanagh could you please share the site URL you would like to turn this on for? @Rasmus Henriksen this isn't in our plans at the moment, thanks for sharing your feedback!

@James Wilson here's a page with some highly requested automations. And in Jira Product Discovery you can navigate to your left nav > Project Settings > Automation > Templates to see some as well.

@Karina Caverly @David Laine I deliberately left it vague so that your free to share what's problematic on your side. If you really want a nudge from me: Any troubles you're having trying to share fields across JPD and Jira Software, or keeping fields in sync across both places.

@KB what's your site URL? Reminder for all: If I've liked your comment then I've turned it on for you, and if you need it turned on please share your site URL as I can't always work it out from your user details.

@Mike Gargano Thanks for sharing your feedback, I've recorded it for future prioritisation. Initially, we're going with the approach of including both epics and stories because that's what's done in Jira Plans for rollups, and most customers we spoke to are trying to replicate this behaviour.

@Alexandre MATHIEU @Valentina Migliore it's currently not in our roadmap to support this for Team-managed projects. Thanks for sharing your feedback, I've recorded it for future prioritisation. If anyone else needs support for team-managed projects, please like this comment.

@eraymond most likely there's a bug with the Automation you've set up. Here's the Automation guide and here's the demo video for this. If you're still running into problems, please create a support ticket by selecting 'Give feedback' at the bottom of the left-nav in Jira Product Discovery.

Hi @Valentina Migliore my best guess is that you're trying to connect to Jira issues in a team-managed project. Currently story point estimates are only supported in company-managed projects. You can see your project type in the bottom left corner of the left-nav in Jira Software. If that's not your issue, then please…

We've turned it on for you @Sierra Gaynor @JJ McKinnon @Mart Postma @Mirko Grahnert @Freyr Guðmundsson. Can I request that you book in a short 30min Zoom call to share your use case and feedback? Here's my Calendly link to book it in. And here's a Loom demo to get you started. @Antal Vig _ Communardo I wasn't able to work…

hi @Johannes Wiedmann we've discovered that this very difficult to fix so we will not be prioritising it for now. If a user has licensed access to Jira Software or they are a JSM agent they will be able to add the issue link, but we are unable to support this for Contributors without that other access in the short term.

Hi Julie, thanks for sharing your suggestion in the Community! How is it helpful to you to have those dates/fix versions from Jira Software reflected in Jira Product Discovery?

Hi @Sierra Gaynor we're actually rolling this out soon! We can get you on the Early Access Program and I'll enable it for you on Monday. Thanks for making my day as a Product Manager, it's so satisfying when we're rolling out a solution just as users ask for it. I'd love to chat to you about how you intend to use the…

@Rohan Parakh ah now I understand, thanks I've recorded your feedback.

@Niki Kavanagh @Karina Caverly could you please share your site URL? eg sitename.atlassian.net

Hi all, thanks for the feedback. We're exploring how we can improve in this area of the product. We'll share more in the Community when we're ready! In the mean time, @Roeland Schoppers @Abby Kiesling would you like to discuss your pain points over a short Zoom call so we can incorporate your feedback in our solution…

hi @Johannes Wiedmann thanks for raising this, it's a use case we haven't thought of. Agreed that the Contributor behaviour should be the same as the Creator. I'm adding this to our backlog to fix.