# Feature OP-20013 - Bidirectional synchronization capabilities for GitLab issues

Project: OpenProject
Status: new
URL: https://community.openproject.org/work_packages/OP-20013

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | Wish List |
| Sprint |  |
| Backlog bucket |  |
| Votes | 1 |
| 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 | Integrations / GitLab |
| 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 OP user of a research team of software developers  
**I want to** have bidirectional synchronization capabilities of GitLab issues and OP work packages  
**so that** I can effectively view, delegate and edit a team&#x27;s large number of tasks for different research projects and programmes across GitLab projects \[and two GitLab instances\] from within OP

**Acceptance criteria**

*   At initialisation, all GitLab issues are imported by prompting the user for or assuming a mapping between GitLab issue fields and OP work package fields
    
*   Changes to GitLab issues across its fields (title, assignee, label, milestone, description are most relevant) are propagated to corresponding OP work packages
    
*   Similarly, changes to OP work packages are propagated to GitLab issues
    

**Technical notes**

*   not insignificant effort may be caused by edge cases (e.g. within ms, the same issue is edited in GitLab and OP simultaneously, possibly causing information to be out of sync)
