Sync customer requests with Jira Product Discovery (JPD)

What is Jira Product Discovery (JPD)?

Jira Product Discovery helps product managers prioritize and manage product ideas by collecting feedback and insights from stakeholders.

Why should you connect Jira Product Discovery (JPD) to Cycle: Key benefits

Customer feedback comes in all forms & shapes (Slack messages, call recordings, screenshots, emails, ...). In many cases, feedback can't be linked directly to an issue and stored in the backlog. You'll rapidly find yourself with a graveyard of issues and a bunch of people expecting an update that they'll never get.

By connecting Cycle to Jira Product Discovery (JPD) you'll be able to

1. Create Jira Product Discovery (JPD) issues automatically from Cycle when you commit to delivering a new feature or addressing a problem.
2. Connect feature requests directly to items on your roadmap. That way you'll reconcile product discovery & delivery workflows
3. Automate status updates between Jira Product Discovery (JPD) and Cycle to close feedback loops with your customers.
4. Push customer context & product documents (scopes, PRDs, etc) to Jira Product Discovery (JPD)

How the Jira Product Discovery (JPD) integration works

When a feature's status changes in Cycle, it triggers Jira Product Discovery (JPD) to create a new issue. The issue's URL is added as a property to the feature in Cycle.

As the issue's status changes in Jira Product Discovery (JPD), the feature's status in Cycle is updated as well. Stakeholders with quotes linked to the feature will automatically receive updates in a feedback loop.

Quick setup

Creating issues and tasks from Cycle:

1. Open your Cycle workspace settings > API > create webhook. Create a webhook that listens for status changes.
2. Filter the webhook events based on the specific status ID change you want to use as trigger.
3. Use the filtered webhook events to create a new issues in Jira Product Discovery (JPD).

1. Setup a webhook in Jira Product Discovery (JPD) to listen to status updates.
2. Based on the task's url, search for the corresponding doc in Cycle.
3. Update the Cycle doc's status property accordingly.