GitLab Integration
Last updated
Last updated
Connecting Leiga work with Gitlab code repositories makes cross-team collaboration easier than ever.
Once integrated, you will be able to:
View Gitlab code commit and merge requests in Leiga work details.
Create Gitlab branches and merge requests from Leiga.
See development performance and code commits reports in Dashboard widgets.
Add Automation that uses Git Push as triggers to automate the development collaboration process.
>>How to integrate with GitLab
Sync activity data between Gitlab and Leiga works by adding Leiga work ID on the commit message.
Expand the GitLab on Leiga work details-"Plug-ins" page to see your code merge request and commit history.
In addition to viewing commits and merge requests, you can also create Gitlab branches and merge requests directly from the Leiga work details.
To create a GitLab branch:
Expand the GitLab icon on Leiga work details-"Plug-ins" page.
Click the + Branch button.
Select the depository and the source branch.
Add the new branch name to create a branch linking with the work.
If your organization is using Gitlab CI/CD, you can also enable Leiga's integration with Gitlab CI/CD to view the pipeline execution status in Leiga.
Leiga standard or above plan is required to unlock this feature
You can view the execution status of associated pipelines in the Build List.
Click Deployments in the project navigator to view GitLab pipeline builds information.
Hover over the status of the pipeline to see the detailed status of each stage.
Leiga's dashboard provides a rich set of widgets to get statistics on your team's work development after you have completed setting up Git integration.
Commit Efficiency: By counting the code submission frequency, you can understand the performance of the developer.
Merge Time Report: Observe the duration distribution of Merge requests for review and problem detection.
Merge Request Statistics: By counting the Merge request frequency, you can observe the performance of the R&D team in the period.
Add Automation to eliminate information lag in cross-team collaboration by using Git Push as triggers.
💡 When a Git commit is created for a {Pending} defect, then change its status to {Fixing}
💡 When a Git commit is created in a {defect} with {fix} in the commit message, then change its status to {pending}