GitHub & Jira Sync

1. The Trigger: GitHub (Issue Opened)

Drag a GitHub trigger onto the canvas. Authenticate and select your target repository. Choose the “Issue Opened” event.

2. The Action: Jira (Create Issue)

Add a Jira action step and select “Create Issue”. Map the incoming GitHub data into the Jira fields:

• Summary: {{ 1.issue.title }}
• Description: Reported by @{{ 1.issue.user.login }} in GitHub: {{ 1.issue.html_url }}, then press Enter for a blank line and add {{ 1.issue.body }}
• Issue Type: Bug (or Task)

A trigger’s fields sit at the top level, which is why every path here starts 1. with no wrapper. Insert them with the Workflow data panel rather than typing them.

3. The Loop-Back: GitHub (Add Comment)

Link the new Jira ticket back to GitHub so the engineer who opened the issue can see it was picked up. Add a second GitHub action step and select “Create Issue Comment”.

The paths below are the shape a Jira Create Issue step typically returns. Confirm yours before you rely on them: run step 2 once, open its Executions tab, and read the actual field names. What sits after the step number is decided by the step, not by Glow, so there is no wrapper you can assume beyond ret.

“Tracking this internally as {{ 2.ret.issue.key }}. You can view the Jira ticket here: {{ 2.ret.issue.url }}”

Create one unmistakable test issue

Open a GitHub issue titled Glow sync test — safe to close with a short body. Run the trigger, then inspect the Jira step’s stored output before configuring the final comment. Insert the returned issue key and URL from the Workflow data panel; do not rely on the example paths if your connector returns another shape.

Check both systems

Confirm Jira contains one issue with the GitHub title, body and source link. Return to GitHub and confirm one comment links to that same Jira issue. If Jira succeeds but the comment fails, check the repository and issue number mapped into Create Issue Comment as well as the Jira output fields.

Set the workflow Live

Close or label the test records according to your team’s convention, switch the workflow to Live, then create one final controlled GitHub issue. Confirm one Jira issue and one GitHub comment are created.