Jira GitHub integration

Integrating Jira with GitHub using Getint connects your project tracking and code management through two-way synchronization. Whether you’re logging issues in Jira or handling code in GitHub, this setup keeps both teams aligned and informed.

This step-by-step guide shows you how to configure the integration using Personal Access Tokens for authentication.

GitHub-Jira Licensing Model

The GitHub-Jira licensing model with Getint is designed to accommodate different integration needs. Here’s an overview:

Standard Licensing

• A Getint license is only required on Jira, allowing seamless data synchronization between GitHub and Jira.

  This makes setup simpler and faster, without the need for additional configurations in GitHub.

Flexible License

• For managed services companies or organizations looking to integrate four or more instances (regardless of whether they are the same or different tools), Getint offers a Flexible License. This custom license covers a specific number of connections (i.e., up to 10 instances) without restrictions on the tools involved. You can also swap the integrated tools while the license remains active, offering unparalleled flexibility.

For more details on licensing, visit our Pricing Page.

Requirements to Build Your Integration:

• The Getint app must be installed in Jira.

• Comments are attributed to the user who created the connection. Therefore, we recommend using dedicated Service Accounts for both instances.

• Jira instances must have a dedicated user and an associated API token with permissions to read, write, view, and modify the project.

• Personal Access Tokens are required for Jira and GitHub authentication. You can find the steps to generate the access token for your connectors here: Connection Guide.

Setting Up Your GitHub-Jira Integration

1. Access the Getint App in Jira

• Navigate to Apps and select Jira - GitHub Integration.

2. Create Integration

• Click Create integration or Migration.

3. Token Generation (Password for Jira Cloud)

• For Jira Cloud, generate a Jira token. This token will act as your password:

  • Go to Atlassian Account Settings.

  • Navigate to Security and generate an API token, then use this token as the password for Jira integration.

4. Generate a GitHub Personal Access Token

• Log in to your GitHub account.

• Select your Avatar in the top right corner. Navigate to Settings > Developer Settings > Personal access tokens.

• Generate a new Token (Classic) or Fine-grained token.

• Provide a name for your token, select the expiration date, and set the required scopes (permissions). For a detailed description of how to create the token, please follow this guide.

• Click Generate Token and make sure to securely store your token, as it will only be visible once.

5. Connect to Jira

• In Getint, enter your Jira instance URL, username, and the API token.

• Use the Personal Access Token for Jira Cloud.

• Follow our Quickstart Guide for more details on how to create the connection.

• Select the Jira project you wish to integrate with GitHub.

6. Enter GitHub Token in Getint

• Once you have generated a Personal Access Token in your GitHub instance, you will now have the option to connect the tool with Getint.

• Paste the GitHub Personal Access Token into the API token field.

• Select the GitHub repository or the Project you want to sync with Jira.

• Click Save to establish the connection.

7. Issue Type Mapping

• Map the Jira issue types you want to sync with GitHub tasks, such as mapping a GitHub Task to a Jira task or a Jira bug to a GitHub task.

• Consider using the Quick Build beta feature for automated type and field mapping, which can streamline the setup process.

8. Field Mapping

• Review or manually map fields within mapped types, including title, description, and assignees.

9. Assignee Mapping

• Use the assignee mapping option to match Jira assignees to GitHub collaborators, enabling precise synchronization of task ownership. For more details, visit our doc: Assignees (users) mapping.

10. Status Mapping

• Map status fields to align between Jira and GitHub. For example, To do in Jira could be mapped to Opened in GitHub.

11. Comments

• When enabling comment synchronization, you can filter by criteria such as created date, author, or visibility (public/private).

12. Filtering:

• It is possible to filter the synchronization to have it customized for your needs and requirements. Please see the doc Items Filtering for more details.

UI Filtering Option:

• Click on the filtering icon near the app icon in your integration. This will apply to that side of the integration.

• Select if the filtering applies to All, New, and Synced items.

• Note that if the option New items is selected, the filtering will apply only to the new items, and the already synced items will continue to sync and update. If the option Synced items is selected, only the already synced items will be updated based on that filter.

• Choose the options and add the value for the filter. It is possible to filter more than one option for each field.

• Select Apply once you have created the filters and Save the integration.

13. Test the Integration

• Create test issues or tasks in Jira or GitHub and observe how they synchronize.

• Ensure that the data between the two platforms is correctly synced.

• Monitor the integration status and the logs in Getint to verify that everything functions as expected.

Conclusion

By following this guide, you can successfully integrate Jira and GitHub using Getint. This setup enables smooth synchronization of issues, tasks, and workflows between development and project management tools, helping teams collaborate more effectively and bridging the gap between developers and project managers.

For further assistance, please contact us at the Support Center or Schedule a Demo.