The GitLab snap-in eliminates the need for manual issue management by connecting DevRev issues with Git actions. By automating issue handling, developers can focus on meaningful work rather than administrative tasks. This approach resonates with those who've encountered problems like delivering patches without proper tracking, spending time updating issue statuses, or finding issue management distracting.

You can link your GitLab commits, branches, and merge requests with existing DevRev issues without automatically creating issues in DevRev. The issues' statuses are guided by GitLab activity, transitioning from In Development to In Review and Closed stages. This ensures comprehensive work tracking and enhances team visibility, minimizing disruptions.

However, if you choose to work in GitLab and never create or link an issue, you shouldn’t have to worry. This snap-in can automatically create issues that track all associated commits, branches, and merge requests. The auto-created issue is populated with the MR description and related GitLab events. The status of these issues is driven by GitLab activity, and the issues will auto-transition stages, from In Development to In Review, and Closed. Your work is always accounted for, and more importantly, your team members have visibility into what you've been up to, resulting in fewer interruptions.