Content
View differences
Updated by Dominic Bräunlein 5 days ago
# User Problem ### Why? (Pain / Problem)
## User Issues are written in OpenProject. Code is written in GitLab. There's no visibility between the two.
* Project manager
* Project member
* Developer
* QA
## Problem
* What should be implemented built is defined in work packages, while packages — but the implementation itself resides lives in GitLab.
* Currently there is only limited visibility between them.
* Users need So whenever someone needs to understand how far along an implementation has progressed, is, where to find the implementation, it, or if it has whether it's already been reviewed.
reviewed, they have to jump into GitLab and manually hunt for the code related to the specification.
That's tedious, and it breaks the flow for everyone involved:
* Specific scenarios include:
A **developer** wants to review the code for a work package.
* A developer wanting **developer** wants to review code.
pick up and continue existing work.
* A project manager wanting **project manager** wants to see the state of the code (e.g., — e.g. is it merged).
merged yet?
* QA wanting **QA** wants to see know where code it was merged to merged, so they know where what to test.
* Determining if A **project manager** wants to demo something and needs to know whether a Merge Request (MR) merge request already exists to create (and whether they could spin up 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. from it).
# Business Case ### What?
## Solution
* Enable We enable users to link **link their code with work packages, packages** — connecting the output developers produce to the project management workflow that tracks it.
Today, OpenProject's GitLab integration only shows merge requests and issues. This makes code activity visible right inside the work package, so teams can follow development without leaving OpenProject.
### How?
* Listen to GitLab push events and link branches and their commits to the work packages they mention.
* Display Store branches and commits with a clear relationship, so each branch shows the commits that belong to it.
* Show the new branch and commit data directly on the work package.
* Update Refresh the merge request and issue views with a the new UI featuring — a clean design and with 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 sections — so all 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> looks consistent.
<br>
## Figma designs -
## User
* Project manager
* Project member
* Developer
* QA
## Problem
* What should be implemented
* Currently there is only limited visibility between them.
* Users need
That's tedious, and it breaks the flow for everyone involved:
## 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
Today, OpenProject's GitLab integration only shows merge requests and issues. This makes code activity visible right inside the work package, so teams can follow development without leaving OpenProject.
### How?
* Display
* Show the
* Update
* 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
<br>
##