# Feature GIT-7 - Display linked GitLab branches on work packages GitLab tab

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

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | 18.0.0 |
| Sprint |  |
| Backlog bucket |  |
| Votes |  |
| List |  |
| Roadmap |  |
| Relevance |  |

## OPEN POINTS / FEEDBACK

_No work packages_

## Features and Chunks

| ID | Subject | Type | Status | Assignee | Target versions | Spent time |
| --- | --- | --- | --- | --- | --- | --- |
| GIT-10 | To save branch data from the push events | Implementation | closed | Yauheni Suhakou |  |  |
| GIT-14 | Delete branches if a MR was merged  | Implementation | rejected |  |  |  |
| GIT-15 | Show branches in the GitLab tab | Implementation | closed |  |  |  |

## Bugs and other work packages

_No work packages_

## Technical Details

| Attribute | Value |
| --- | --- |
| Module | Integrations / GitLab |
| Feature Flag |  |
| Requires doc change | No |
| Enterprise plan | Community (COM) |

## Details

| Attribute | Value |
| --- | --- |
| Pull preview |  |
| Mockups |  |
| Accessibility | No |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Developers |  |
| Designer |  |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| PD (min) |  |
| PD (max) |  |
| Work |  |
| Labor costs |  |

## Description

**As a** developer (and project manager / QA)  
**I want to** see the list of branches linked to a work package  
**so that** I can tell whether implementation has started, find the branch to continue or review, and open it directly in GitLab — without searching the repository by hand.

####   

**Acceptance criteria**

*   A work package shows all branches whose name references it.
    
*   A work package with no branches shows an empty state (no broken/empty section).
    
*   When a branch is deleted in GitLab, it disappears from the list (MR is merged, for example; branch is manually deleted) 
    
*   No activity should be created
    
*   It should be possible to create a MR from this branch
    

**Technical notes**

*   <br>
    

**Permissions and visibility considerations**

*   A user who could see the WP should be able to see GitLab branches also
    
*   _When is it not visible?_
    

**Translation considerations**