Asana GitLab integration
Integrating Asana and GitLab
Connecting Asana with GitLab synchronizes project management data with development records, ensuring technical and sales teams remain aligned. This integration automates updates between platforms, eliminating manual data entry and reducing the risk of cross-departmental discrepancies.
Asana GitLab Licensing Model
The Getint licensing model for Asana and GitLab focuses on predictable costs and scalability:
Standard Licensing
This tier covers a direct integration between one Asana instance and one GitLab instance for a fixed fee. It includes unlimited project and work item synchronization without hidden charges.
Network License
Designed for managed service providers or large organizations, this option supports three or more instances. It allows for a specific number of connections (e.g., up to 10 instances) and provides the flexibility to swap integrated tools while the license is active.
For more details on licensing, visit our Licensing Page.
Requirements to Build Your Integration:
Deployment Options: Getint provides two ways to host your integration: a managed SaaS platform or a self-hosted On-premise version. More information about Getint On-premise here.
Authentication: Both Asana and GitLab require Personal Access Tokens to establish a secure connection. You can find the steps to generate the access token for your connectors here: Connection Guide.
Service Accounts: Because the integration attributes comments to the user who created the connection, we recommend using dedicated Service Accounts for both instances to maintain a clear distinction between automated updates and individual user activity.
Setting Up Your Asana GitLab Integration
1. Access the Getint App
Log in at app.live.getint.io. If you do not have an account, click Sign up to create one.
Enter your details, select the apps you want to connect, and click Create new workspace.
After you create the workspace, go to it to launch Getint.
The Getint interface will load.
2. Create an Integration
Go to Workflows (lightning bolt icon), and click Create Integration. From this menu, select Continuous Sync or Data Migration.
3. Generate an Asana Personal Access Token
Log in to Asana and follow the video below to generate your Access Token.
4. Generate a GitLab Token
Log in to your GitLab account. In the top-left or top-right corner (depending on your version), click on your Avatar/Profile Picture and select Preferences.
In the left-hand sidebar, look for the Access section (usually near the top) and select Personal access tokens.
Click the Generate token button to open the configuration form. Make sure to use the Legacy token, as we don’t support fine-grained tokens.
For specific permissions, please follow the video tutorial below:
5. Connect to Asana
In Getint, click on Connect App and choose Asana.
Enter your Access Token for Asana.
Select the project you wish to integrate with Asana.
You can only select one project when syncing with GitLab. Selecting multiple projects will cause GitLab to disappear from your available integration options.
Click Connect to establish the connection.
6. Connect to GitLab
Click on Connect App and choose GitLab. Enter your GitLab instance URL (if using GitLab On-premise), then enter the generated Access token and click Next.
Add the connection and select it.
7. Select GitLab Project
Select the established GitLab connection and choose the project you want to integrate with.
8. Configure Type Mapping
Quick Build: Automatically map fields and types between applications with this feature.
Manual Mapping: Use this feature for full control over the integration. Select +Add Type Mapping to define your types, such as Incident, Task, or Issue.
Example: Task ↔ Issue.
9. Field Mapping
Review or manually map fields within mapped types, including title, description, and assignees.
Ensure synchronization flow is defined for each field, using the arrows and selecting Apply.
Unlike Assignees, Reporters are not supported in this integration because they are read-only on both platforms, and read-only fields cannot be modified.
10. Assignee Mapping
Use the assignee mapping option to match GitLab assignees to Asana assignees. For more details, visit our doc: Assignees (users) mapping.
11. Status Mapping
Map status fields to align between GitLab and Asana. For example, To do in Asana could be mapped to Opened in GitLab.
You can also configure the status direction to support unidirectional transitions instead of bidirectional updates.
12. How to Manage Comments & Attachments:
The Comments are enabled by default. You can configure these settings to match your organization’s needs, such as selecting unidirectional or bidirectional sync and filtering by criteria like creation date, author, or visibility (public/private).
For attachments, toggle on the Synchronize attachments setting. You will notice that you need to enter a cookie header.
Inline images aren’t supported for the Description field.
To locate your GitLab Cookie, open your GitLab Groups page, right-click, and select Inspect. Navigate to the Network tab and refresh the page to capture the network activity. Next, select the entry named groups from the list of requests. You can then retrieve the required value by viewing the Cookie field under the Request Headers section of the Headers tab.
Sometimes the developer tools won't display any data for the cookie header. To fix this, click on your Group or Project, and this should make the options visible.
Copy the information and paste it into the GitLab Cookie Header field in Getint. Click Apply to submit the changes and save your integration.
Ensure to test the attachments after enabling them.
Currently, attachments are only supported one way from GitLab to the other app in the integration. Also, there is no API available to download and upload attachments via a GitLab integration. As a result, this alternative remains the only option for downloading attachments from synced comments, provided they come from GitLab.
13. Advanced Tab
Enable Customize create/update actions to manage item synchronization. This allows for specific rules, such as one-way creation for the left application combined with bidirectional updates.
14. 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 after creating the filters and Save the integration.
15. Test the Integration
Create test issues or tasks in Jira or Asana 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
Following this guide lets you set up the Jira-Asana integration with Getint. This configuration supports data synchronization of issues, tasks, and workflows across development and project management tools, allowing teams to collaborate while connecting developers and project managers.
For further assistance, please contact us at the Support Center or Schedule a Demo.
Last updated
Was this helpful?