GitHub to Jira Issue Creation

1. The Trigger: GitHub (New or Updated Issue)

Drag a GitHub trigger onto the canvas and select your target repository. Choose New or Updated Issue (Instant) (filtered to opened in Filter Event Types) or New or Updated Issue (Polling).

Use this sample in the trigger’s Test & Debug tab to practice mapping. Your GitHub trigger’s payload may differ, and you should not run the comment action against this placeholder issue number:

{
  "action": "opened",
  "issue": {
    "number": 42,
    "title": "Authentication fails with 401 on token refresh",
    "body": "When a session token expires, the refresh endpoint returns 401 instead of generating a new token pair.",
    "html_url": "https://example.com/issues/42",
    "user": {
      "login": "octocat"
    }
  }
}

2. The Action: Jira (Create Issue)

Add a Jira action Step and select Create Issue. Keep the Step’s Mode in the ⋮ menu set to HTTP to configure its fields manually. Choose the Connection, Cloud ID, Project ID, and Issue Type (such as Bug or Task). In Additional properties, supply the summary and description for the sample above:

• summary: {{ 1.issue.title }}
• description: Reported by @{{ 1.issue.user.login }} in GitHub: {{ 1.issue.html_url }}\n\n{{ 1.issue.body }}

These paths match the sample and assume the trigger is Step 1. Once you connect your repository, capture a test issue event on the trigger. Then pick its fields from Workflow data to match your repository’s exact payload.

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

Add a second GitHub action Step and select Create Issue Comment. Choose the same repository and map the issue number ({{ 1.issue.number }} in the sample).

Save a real test issue payload on the trigger, set the run point to the trigger, and click Run in the dock once. Native app actions return fields directly without a ret wrapper. Pick the returned Jira key from Workflow data (such as Tracking this internally as plus the key), then connect the comment Step.