GitHub
Getint: Simplifying GitHub Integration and Data Synchronization
Getint facilitates seamless integration between multiple platforms, enabling synchronization across tools like GitHub, Jira, Asana, and Azure DevOps. It supports both SaaS and On-Premise deployment, offering adaptability to suit diverse business requirements.
Key Topics Covered:
By synchronizing data across instances and platforms, Getint empowers users to efficiently track and manage tasks while integrating GitHub with other project management tools.
Installing and Configuring Getint for GitHub
Getint simplifies connecting and migrating data between systems. Below are the steps to get started:
Step 1: Access Getint
Want to integrate Jira with GitHub? Just download the app from the Atlassian Marketplace. It’s quick and easy! You can find it here: GitHub Integration for Jira.
Other tools: Select between Getint On-Premise or SaaS options.
Step 2: Set Up a Connection with GitHub
Ensure you have the correct access permissions. Here you will find all the steps to generate an access token in GitHub: Generating a GitHub Token.
Choose GitHub as the app, create a new connection, and enter your GitHub access token.
Step 3: Connect to Another Tool
Choose the platform you want to integrate with GitHub, such as Jira.
Step 4: Map Types and Fields
Match GitHub issue types, such as Tasks, with their equivalents in the other tool.
Leverage the Quick Build feature for automatic mapping, or adjust mappings manually to fit your needs.
If you need help with setup or run into any challenges, our support team is always here to assist.
For additional guidance on using Getint with GitHub, refer to:
Setting Up a Git Repository Integration
Configuration Steps
Create a Git Connector Integration: Navigate to the Getint dashboard and select Git Connector. Choose GitHub as your app.
Authenticate with GitHub: Generate an access token. Grant access to the repositories you want to sync.
Set up OAuth for Jira: Unlike Continuous Syncs or data Migrations, Git integrations need OAuth setup directly within your Jira environment. Follow the steps outlined in our guide: Connection | Jira OAuth.
Select Repositories: Choose one or more GitHub repositories to link with Getint. You can sync issues, pull requests, and commits.
Test & Activate: Run a test sync to verify everything works as expected. Once confirmed, activate the integration.
Sync Your Branches: Use the correct prefixes outlined in our Git Integration article to sync the branches, commits, and pull requests.
Supported GitHub Fields
Getint allows you to map fields between different platforms, and here's a list of our currently supported:
How Field Mappings Work:
One-Way Mapping:
When you update fields in one of the synced apps, those changes will appear in the other app. However, updates made in the other app won’t affect the first app because the fields are read-only.
Two-Way Mapping:
Updates to synced fields will be reflected in both apps. If you modify a field in one app, the change will automatically sync to the other app as well.
Tip:
While technically it's not possible to directly modify read-only fields, we offer a solution to achieve bidirectional integration or migrate these fields using custom fields. Setting up this solution requires specific steps, but it is indeed possible. You can find more detailed information in this article.
GitHub Field
One Way
Both Ways
Assignee
✔️
✔️
Author
✔️
Comments
✔️
✔️
Description
✔️
✔️
ID
✔️
Labels
X
X
Title
✔️
✔️
Important Note: While we make every effort to ensure the accuracy of this list, please be aware that supported fields may differ in the original product.
Key Considerations
At Getint, we are committed to continuously updating our supported features, fields, and compatible apps. However, please keep the following key points in mind:
Attachments: You can sync attachments from GitHub to Jira by providing S3 credentials.
Change History: Getint cannot integrate the history of changes.
Comments: Comments added by Getint will appear under the user account you choose during connection setup. Consider creating a dedicated Service Account for integration to maintain consistency. The original author’s name will appear in the comment footer, but the comment will be assigned to the connecting account. Also, comments and attachments transferred from GitHub to Jira will be set to public or private (they will be public by default). You can configure Jira to mark all comments from GitHub as private automatically. However, enabling both public and private visibility options is impossible.
Custom fields: Currently, there’s no support for custom fields.
Inline images aren’t supported.
Labels aren’t supported.
Contacting Our Support Team
Our dedicated Support Team is here to assist with your integration and migration needs. Whether you have questions or seek deeper insights into our solution, you’re welcome to schedule a demo call with us.
Case Studies
Discover how Getint enhances tool integration for businesses of all sizes. Our Case Studies highlight real-world solutions designed to empower teams and organizations.
Last updated
Was this helpful?