# Epic GIT-3 - GitLab code activity in work packages tab

Project: Stream Repositories
Status: closed
URL: https://community.openproject.org/work_packages/GIT-3

## Detailed specification

### Motivation and background information

*   What should be implemented is defined in work packages, while the implementation itself resides in GitLab.
    
*   Users must go to GitLab and exhaustively/manually find the code related to the specification, which is annoying and inefficient.
    
*   Today, OpenProject's GitLab integration only shows merge requests and issues, lacking deeper code activity visibility.

### Acceptance criteria

*   Show commits, branches, merge requests, issues in GitLab work package tab
    
*   Allow creation of merge requests in work package tab
    
*   Keep existing functionality of Git snippets

### Out of scope

*   Homogenize with GitHub integration
    
*   OAuth connection
    
*   Refined admin UI

| Attribute | Value |
| --- | --- |
| Mockups | https://www.figma.com/design/MUkwDhlspEfdBBbockeMxt/GitLab-Integration?node-id=2001-914&p=f&t=HFkM8T4A90trUJj2-0 |

## Planning

| Attribute | Value |
| --- | --- |
| Roadmap | 2026 Q4 |
| Date |  |
| Votes |  |
| List |  |
| Target versions | 18.0.0 |
| Sprint |  |
| Backlog bucket |  |
| Relevance |  |

## Subitems

| ID | Type | Subject | Status | Assignee | Target versions | Project | Priority | Spent time |
| --- | --- | --- | --- | --- | --- | --- | --- | --- |
| GIT-4 | Feature | Introduce commits list | closed |  | 18.0.0 | Stream Repositories | Medium |  |
| GIT-5 | Feature | Improve merge requests list | closed |  | 18.0.0 | Stream Repositories | Medium |  |
| GIT-6 | Feature | Improve issues list | closed |  | 18.0.0 | Stream Repositories | Medium |  |
| GIT-7 | Feature | Display linked GitLab branches on work packages GitLab tab | closed |  | 18.0.0 | Stream Repositories | Medium |  |
| GIT-9 | Feature | Create a new UI for GitLab tab | closed |  | 18.0.0 | Stream Repositories | Medium |  |
| GIT-20 | Open Point | Do we need a demo instance?  | decided |  |  | Stream Repositories | Medium |  |

## Bugs and other work packages

| ID | Type | Subject | Status | Assignee | Target versions | Module |
| --- | --- | --- | --- | --- | --- | --- |
| GIT-21 | Bug | Merge Requests / Issues change "created by" after updates | closed |  | 18.0.0 | Integrations / GitLab |
| GIT-20 | Open Point | Do we need a demo instance?  | decided |  |  |  |

## Details

| Attribute | Value |
| --- | --- |
| Module | Integrations / GitLab |
| Enterprise plan | Community (COM) |
| Labels |  |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable | Dominic Bräunlein |
| Product manager | Nova Bonic |
| Designer | Marc Alcobé |
| Developers | OP Dev Titan Team |
| Requested by |  |
| Interest by |  |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| Work |  |

## Description

# User Problem

## User

*   Project manager
    
*   Project member
    
*   Developer
    
*   QA
    

## Problem

*   What should be implemented is defined in work packages, while the implementation itself resides in GitLab.
    
*   Currently there is only limited visibility between them.
    
*   Users need to understand how far an implementation has progressed, where to find the implementation, or if it has already been reviewed.
    
*   Specific scenarios include:
    
    *   A developer wanting to review code.
        
    *   A project manager wanting to see the state of code (e.g., is it merged).
        
    *   QA wanting to see where code was merged to know where to test.
        
    *   Determining if a Merge Request (MR) already exists to create a pull preview for a project manager demo.
        

## Pain

*   Users must go to GitLab and exhaustively/manually find the code related to the specification, which is annoying and inefficient.
    
*   Today, OpenProject's GitLab integration only shows merge requests and issues, lacking deeper code activity visibility.
    

# Business Case

## Solution

*   Enable users to link their code with work packages, connecting the output developers produce to the project management workflow that tracks it.
    
*   Listen to GitLab push events and link branches and their commits to the work packages they mention.
    
*   Display the new branch and commit data on the work package.
    
*   Update the merge request and issue views with a new UI featuring a clean design and collapsible elements.
    
*   Allow users to create Merge Request directly in OpenProject
    

# Launch and Growth

## Measures

*   Reduction in time spent manually searching for code related to specifications.
    
*   Increased ability for Project Managers, Developers, and QA to verify code status (merged, reviewed, existing PR/MR) directly within OpenProject.
    

## Messaging

<figure class="table op-uc-figure_align-center op-uc-figure"><table class="op-uc-table"><tbody><tr class="op-uc-table--row"><th class="op-uc-table--cell op-uc-table--cell_head"><p class="op-uc-p">Headline</p></th><td class="op-uc-table--cell"><p class="op-uc-p">Connect Code to Workflow: Full GitLab Visibility Inside OpenProject</p></td></tr><tr class="op-uc-table--row"><th class="op-uc-table--cell op-uc-table--cell_head"><p class="op-uc-p">First Paragraph</p></th><td class="op-uc-table--cell"><p class="op-uc-p">Stop switching between tools. We now enable you to link branches and commits directly to your work packages, making code activity visible right inside OpenProject so teams can follow development seamlessly.</p></td></tr></tbody></table></figure>

##