Automation library · Customer support

Auto-resolve Jira tickets with GitHub Copilot and Port Context

Started by an event in a connected app, and works across GitHub and Jira. 9 steps, 2 branches: a working afternoon to understand properly.

Medium

9 stepsMedium: a working afternoon
2Branches: places the flow splits
0Loops or waits
2Services it connects to

The flow

Starts it 1Logic 2Service 6

The steps in the order they run, from what starts it.

  1. 1On Jira ticket updatedJira triggerStarts it
  2. 2Is ready for assignment?IfLogic
  3. 3Extract context from PortPort Api AiService
  4. 4Parse Port AI responsePort Api AiService
  5. 5Create a GitHub issueGithubService
  6. 6Is issue creation successful?IfLogic
  7. 7Assign issue to CopilotGithubService
  8. 8Add issue link to Jira ticketJiraService
  9. 9Mark ticket as assignedJiraService

How it's built

Starts on
An event in a connected app
Steps
9, with 2 branches
Size
Medium: a working afternoon
Connects to
GitHub, Jira
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

An n8n account, plus your own GitHub and Jira accounts. You connect your own accounts after importing it; none are included.

What starts it?

It starts on an event in a connected app.

Does it use AI?

No. Every step is fixed logic or a call to a service, so it does the same thing every time.

How long does it take to set up?

Plan an afternoon. 9 steps is enough that you should read each one before running it.

How do I import it?

Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.

Before you run it

Nothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 9 steps before you point it at anything that matters.