Sync GitHub Issue to Atlassian JIRA Issue
Tags: github, atlassian, jira, tutorial
Published: 2021-03-26 09:29:21

---
title: Sync GitHub Issue to Atlassian JIRA Issue
published: true
date: 2021-03-08 10:19:38 UTC
tags: #github, #atlassian, #jira, #tutorial
canonical_url: https://tech.forums.softwareag.com/t/sync-github-issue-to-atlassian-jira-issue/239486
---

## Summary

This article describes a business use case to sync the issue created in **GitHub** to the issue in **Atlassian JIRA**.

## Prerequisites

- User should have a working [webMethods.io](http://webMethods.io) Integration tenant.

- User should have a working **GitHub** and **JIRA** account.

## Steps

1. Login to [webMethods.io](http://webmethods.io/) Integration tenant and create a Workflow.

2. Click the **Settings** and search for **GitHub** trigger from the available list of triggers.

3. Select **New Issue** from the list of **Select Trigger** options. Authorize **GitHub** by either default or manual configuration, then select the **Repository Name**.
![image](https://aws1.discourse-cdn.com/techcommunity/optimized/2X/b/b835bfb97b1f92cf2e2544d071b68b9b1854d4ca_2_690x388.png)
4. Click **Save** , skip testing the trigger for now, then click **Done**.

5. Drag and drop the **Atlassian JIRA** connector to the workflow palette.

6. Double click on the **JIRA connector** icon in the workflow palette to configure the action.

7. In the action configuration screen, click the **+** under **Select Action** to create a custom action.
![image](https://aws1.discourse-cdn.com/techcommunity/optimized/2X/a/ab3a7bc60560d39fea7ac9448edda38465d84218_2_642x500.png)
8. Select authentication type and connect to the **Atlassian JIRA** by providing the necessary credentials.

9. Provide a name to the custom action, then select **JIRA Platform** as the functional area
![image](https://aws1.discourse-cdn.com/techcommunity/optimized/2X/3/3716b20a683264e2f95eefb77bf9d15ddfece453_2_690x354.png)
10. Select **Create Issue or Subtask** as the operation and task (for a specific project) as the business object. Then, select the required data fields.
![image](https://aws1.discourse-cdn.com/techcommunity/optimized/2X/7/7aa541af76b1f6dab5e7135e3a6dbd90cbd8a5ef_2_690x347.png)
![image](https://aws1.discourse-cdn.com/techcommunity/optimized/2X/8/889913c89fedef79678d51e33a1476938ae4a4c6_2_690x359.png)
![image](https://aws1.discourse-cdn.com/techcommunity/optimized/2X/e/e407d683f3950fd7da43de99870acd180c1ab5c4_2_690x386.png)
11. Click **Next** , then **Done**.

12. Once the custom action is created, click **Next**.

13. Map the appropriate fields from the **GitHub** trigger to the **JIRA** connector fields.
![image](https://aws1.discourse-cdn.com/techcommunity/optimized/2X/3/30c77f925d5223501b4bdb8f7d129f6b25d6b3fe_2_690x353.png)
14. Click **Next** , then **Done**. Save the workflow.

15. Now, create a new issue in the **GitHub**. Use the same repository selected in step 3.
![image](https://aws1.discourse-cdn.com/techcommunity/optimized/2X/7/7bd05ea17410a4ac4a7b40a0acc041c7718dc8cb_2_690x305.png)
16. Soon the issue is submitted the workflow will execute.
![image](https://aws1.discourse-cdn.com/techcommunity/optimized/2X/7/78ca50cb4b6259333a95ecb584d4cd1601ae6fd2_2_690x305.png)
17. Now check the **Atlassian JIRA** account for the same issue created.
![image](https://aws1.discourse-cdn.com/techcommunity/optimized/2X/d/d4fd9c2aa89c5cc77c25f26eba6cf66fc374fd6d_2_690x322.png)

[Read full topic](https://tech.forums.softwareag.com/t/sync-github-issue-to-atlassian-jira-issue/239486)