# Feature COMMS-731 - Adapt GitHub and GitLab modules for semantic identifiers

Project: Stream Communicator
Status: closed
URL: https://community.openproject.org/work_packages/COMMS-731

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | High |
| Target versions | 17.5.0 |
| Sprint | BlockNote Update; Finishing Identifiers; Starting Versions |
| Backlog bucket |  |
| Votes |  |
| List |  |
| Roadmap |  |
| Relevance |  |

## OPEN POINTS / FEEDBACK

_No work packages_

## Use cases

_No work packages_

## Features and Chunks

_No work packages_

## Bugs and other work packages

_No work packages_

## Technical Details

| Attribute | Value |
| --- | --- |
| Module | Integrations / GitHub, Integrations / GitLab |
| Feature Flag |  |
| Requires doc change | Yes |
| Enterprise plan |  |

## Details

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

## People

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

## Estimates and progress

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

## Description

**As** a developer&nbsp;  
**I want to** see my GitHub/Gitlab issues and PRs linked to the correct WP by mentioning its ID or URL in the body.

**Acceptance criteria**

*   If the instance is set to project-based work package identifiers
    
    *   project-based semantic identifiers are used for the Git Snippets (tab in work package show view)
        
    *   Incoming webhooks should still work and identify the correct work package
        
*   A bitbucket integration (external contribution) was announced, this should be adapted as well if it is already merged
    

**Technical notes**

*   <br>
    

**Permissions and visibility considerations**

*   _To whom is this feature visible?_
    
*   _When is it not visible?_
    

**Translation considerations**

*   _Key terms and phrases in the key languages_ 
    

**Out of scope**

*   <br>
    

_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of the changes._
