# Feature OP-14607 - Allow GitHub and GitLab integration to tightly couple PRs/MRs with a work package

Project: OpenProject
Status: in specification
URL: https://community.openproject.org/work_packages/OP-14607

## Planning

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

## OPEN POINTS / FEEDBACK

_No work packages_

## Features and Chunks

_No work packages_

## Bugs and other work packages

_No work packages_

## Technical Details

| Attribute | Value |
| --- | --- |
| Module |  |
| Feature Flag |  |
| Requires doc change | No |
| Enterprise plan |  |

## Details

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

## People

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

## Estimates and progress

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

## Description

As a software developer organizing work in OpenProject and GitHub/GitLab using PRs/MRs I struggle to keep both sides in sync.

I would like to be able to allow the GitHub/GitLab integration to

  - update the *assignee*, when a reviewer is chosen so that the information is not contradicting (needs mapping of users between systems. A user in OP could track their GitHub or GitLab handle in their profile. A verification of it would be good.)
  - update the *status* of the WP to "needs review", when a reviewer was chosen on the PR/MR (needs configuration of the WP type)
  - update the *status* of WP when a PR gets merged are closed
  - save the merge commit on the WP for the merging of a PR/MR so that we can use that for further processing, e.g. tracking of deployment of a new feature or bug fix and setting future status of the WP according and write journal entries.
  - assign the *version* of a WP according to the *base* branch (needs some rule on how to set version based on base branches)

It might be that is a candidate for Automation as described <mention class="mention" data-id="37473" data-type="work_package" data-text="##37473">##37473</mention>
