Auto-resolve Jira tickets with GitHub Copilot using Port Context
UnknownUnknown. This template uses community nodes we can't verify statically. Uses community nodes that can't be verified statically (unverified community packages are off by default in 3.0). Static check, last run 2026-10-19.
What this workflow does
This workflow has 9 nodes and runs on Jira events (jira:issue updated). Along the way it connects GitHub, Jira Software and Portio Experimental (community).
How it runs
Trigger: On Jira events (jira:issue updated).
- Is ready for assignment? (If): checks a condition and branches into true / false
- Extract context from Port (Port Api Ai): general invoke
- Parse Port AI response (Port Api Ai): get invocation
- Create a GitHub issue (GitHub): uses GitHub
- Is issue creation successful? (If): checks a condition and branches into true / false
- Assign issue to Copilot (GitHub): create comment
- Add issue link to Jira ticket (Jira Software): work with issue comment
- Mark ticket as assigned (Jira Software): update
Services it uses
Before you upgrade to n8n 3.0
We can't fully verify this one: it relies on 1 community package, and n8n 3.0 turns unverified community packages off by default (N8N_UNVERIFIED_PACKAGES_ENABLED=false).
- Check that @port-labs/n8n-nodes-portio-experimental is verified or supports 3.0 (used in Parse Port AI response, Extract context from Port).
Nodes used (5)
- If
n8n-nodes-base.if - GitHub
n8n-nodes-base.github - Jira Software
n8n-nodes-base.jira - Jira Trigger
n8n-nodes-base.jiraTrigger - Port Api Ai
@port-labs/n8n-nodes-portio-experimental.portApiAi
From the author
Auto-resolve Jira tickets with coding agents Coding agents can significantly speed up development, but crucial engineering context often gets lost in the process. This guide demonstrates how to use Port as a context lake in n8n workflows to automatically…