🎥 "How to connect discovery and delivery in Jira" webinar - recording + top FAQ

[#1]

Thank you to everyone who participated in our webinar "How to connect discovery and delivery in Jira"! For those of you who were unable to attend, you can now watch the recording on demand here: https://www.atlassian.com/webinars/software/how-to-connect-discovery-and-delivery-in-jira.

Below you will find answers to the top FAQ during the event. 👇

Thanks for watching!

FAQ

1. How do you sync between Jira Product Discovery and Jira Software for tracking during the delivery phase?

You can easily connect your ideas to issues in Jira Software via the delivery tab within an idea view. You can either create a new ticket or connect an idea to an existing ticket, and then easily track the delivery progress using the "delivery progress" field. Learn more here.

2. What are the best practices for managing, categorizing, and prioritizing a large volume of ideas in Jira Product Discovery to keep a list view organized and efficient?

Here are a couple of different resources that can help:

• Demo: using fields and views to organize a large list of ideas
• 1h webinar: how to uplevel your product discovery practice with Jira Product Discovery.

3. How can we collect insights and feedback from internal and external sources and directly add them to Jira Product Discovery? Can we connect insights to multiple ideas?

There are a few ways that you can add insights from your existing workflow:

• Use our Chrome extension. Learn more here.
• Create feedback channels with customers/internal teams. You have a few options:
  • Set up a Jira Service Management queue

  • Set up a dedicated Slack channel #product-feedback (also works with Teams)

  • Share views with other teams and gather their feedback

• Use one of our third-party integrations.

Presently, you cannot connect insights to multiple ideas.

4. How does Jira Product Discovery work with Jira Plans?

Learn more here.

5. What are the different permissions of creators vs. contributors? Can external stakeholders view roadmaps without a Jira license?

See the below table for more information on creator vs. contributor permissions.

With our recently released Publish feature, you can now share views with external, as well as internal, stakeholders. Please note this feature is only available in the Standard edition of Jira Product Discovery. Learn more here.

6. How does Jira Product Discovery integrate with other Atlassian products like Confluence and Jira Service Management, as well as with third-party tools?

• Here is a demo for how to use Confluence and Jira Product Discovery
• Here is a demo for how to use Atlas goals and projects in Jira Product Discovery

• Set up a Jira Service Management queue to receive feedback from customers and internal teams

• Learn about our other integrations here.

7. How can we export data or create shareable views for external sharing?

Learn more about exporting options here.

With our recently released Publish feature, you can now share views with external stakeholders without a Jira license. Learn more here.

8. What are the licensing requirements and costs associated with Jira Product Discovery? Is there a free version or trial available?

Jira Product Discovery is a standalone product and requires its own license. You pay for the number of creators on your plan: $0/creator on a Free plan and $10/creator on a Standard plan. Learn more about the different plans here.

We have both a free version and a 14-day trial on our Standard plan. Learn more about the trial here.

9. Are there plans to introduce AI to Jira Product Discovery?

Yes, and we will have a Community post about this soon!

[Selena Peri]

Kia Ora, 
Instead of linking JDP "Idea" into a JSP "Epic" via "create delivery ticket" - how would this be set up in a automation rule, pulling across particular data field points (e.g. Summary)?
I am successful in creating an Epic issue off a JDP in my JSP.

I've tried to create automation rule as follows with no successful luck of creating a Epic in my JSP:

When: JDP issue transitioned to: xxx (from any status)
Then: Crate a EPIC (in JSP)
          Copying the "trigger issues' Summary (trigger issue type = Idea, in JDP)
          And, transition 'target issue' (new Epic created in JSP) to: xxx

Thanks!

[Rohan Swami]

Hi @Selena Peri there's a full guide on Automation here including keeping your idea and epic descriptions in sync. You should be able to combine your existing Automation with those from the guide. 

[Till]

Hi @Rohan Swami thanks for all of the useful information.
It is really helpful to see best practices, since we don't have a lot of discovery experience in our organization until now.
At 29:27 you mention the live embed of the fields from JPD to Jira.
Does it mean that we could use the fields e.g. for ranking in Jira or work with them in any way we want to?
And do you have an estimation when this feature will go live?

[Rohan Swami]

Hi @Till I can't offer timeframes, it's ready as soon as it's ready! It would be great to get your feedback on our solution so that we can make sure that it's going to solve the job for you. Can you book in a short Zoom call with me on Calendly?

[Carsten David]

Hi @Rohan Swami

I have linked the start date of the linked delivery ticket to my discovery board succesfully in the way you explained it in the video at 42:40. I wanted to link the due date as well but it is not shown in the list of available date fields. In the delivery ticket the due date is available. Do you have an idea what I have to check / change to solve this without creating a complex rule?

Tanks!

[Rohan Swami]

@Carsten David It should be appearing as an option! Can you please create a support ticket and we'll take a look: Left panel in Jira Product Discovery > Give feedback > I want to ... Get help from the support team.