How can Jira Product Discovery APIs and automation be used for an open-source blockchain infrastruct

[KoKyat]

I am designing an open-source blockchain infrastructure workflow and want to understand how Jira Product Discovery can be integrated with external developer and infrastructure systems.

The workflow may include:

- GitHub repositories and pull requests
- Jira issues and projects
- Confluence documentation
- API-driven automation
- CI/CD pipelines
- Developer activity
- Product discovery and roadmap items
- Governance and approval workflows
- Public documentation and project status

I am particularly interested in:

1. Jira Product Discovery REST API capabilities
2. Creating and updating ideas programmatically
3. Linking GitHub pull requests and issues to Product Discovery ideas
4. Webhooks and event-driven automation
5. Integrating Jira, Confluence, GitHub and external APIs
6. Authentication and API token best practices
7. Using JPD as an API-driven product intelligence layer
8. Recommended architecture for maintaining a public open-source project roadmap

Are there recommended API patterns, webhooks, automation rules, Forge apps, or other Atlassian integration approaches for this type of workflow?

[Andrea Robbins]

I have built all sorts of solutions relating to this topic. Before providing ideas, I would like to know your use cases, goals, and perceived benefits you want to get out of the tool. That’s what will shape the best path forward. 

[Joseph K_ Little]

A good approach would be to use Jira Product Discovery as the product intelligence and roadmap layer, while Jira manages engineering work, GitHub handles code and pull requests, and Confluence stores documentation.

For automation, Jira REST APIs, GitHub webhooks, Atlassian Automation, and Forge can connect these systems. I’d recommend using shared issue/idea IDs, event-driven workflows, and clear ownership of data instead of syncing everything both ways.

It would also be helpful to confirm which JPD features - especially ideas, insights, links, and delivery data - are currently available through supported REST APIs.