Content
View differences
Updated by Yauheni Suhakou 4 days ago
**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**
**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**