Problem
The jira-issue-to-pr automation currently declares the jira integration, but that catalog entry is HTTP/OpenAPI-only. Canvas treats recommended automation requirements as MCP integrations, so the Jira requirement is silently omitted from the UI.
Atlassian provides an official hosted MCP server through Atlassian Rovo. The extensions catalog already contains this as atlassian-rovo with the endpoint:
https://mcp.atlassian.com/v1/mcp/authv2
Proposed fix
Update the jira-issue-to-pr automation to require the appropriate Atlassian MCP integration (atlassian-rovo) and adjust its requirement message and setup instructions accordingly.
The skill should also be checked so its runtime instructions and credential expectations match the MCP-based integration rather than assuming direct Jira REST credentials.
Related Canvas issue: OpenHands/OpenHands#16292
Problem
The
jira-issue-to-prautomation currently declares thejiraintegration, but that catalog entry is HTTP/OpenAPI-only. Canvas treats recommended automation requirements as MCP integrations, so the Jira requirement is silently omitted from the UI.Atlassian provides an official hosted MCP server through Atlassian Rovo. The extensions catalog already contains this as
atlassian-rovowith the endpoint:https://mcp.atlassian.com/v1/mcp/authv2Proposed fix
Update the
jira-issue-to-prautomation to require the appropriate Atlassian MCP integration (atlassian-rovo) and adjust its requirement message and setup instructions accordingly.The skill should also be checked so its runtime instructions and credential expectations match the MCP-based integration rather than assuming direct Jira REST credentials.
Related Canvas issue: OpenHands/OpenHands#16292