# Feature OP-20336 - Scheduled soft sync and manual hard sync for GitHub integration

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

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | Wish List |
| Sprint |  |
| Backlog bucket |  |
| Votes | 2 |
| 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 / GitHub |
| 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** an OpenProject admin  
**I want** OpenProject to perform an hourly GitHub sync via a background job, plus a manually triggered hard sync job  
**so that** the hourly &quot;soft sync&quot; checks all associated repositories for changes since the previous sync, and the &quot;hard sync&quot; lets me fully reconcile development data when webhooks were missed or data drifted.

Note: These features address the cases where the already configured WebHook on the Github side fails partially to send data to OpenProject due to network issue, down time etc....

**Acceptance criteria**

*   A background job runs hourly (soft sync) across all repositories linked to OpenProject projects and work packages.
    
*   Soft sync is incremental: it fetches only pull requests, commits, branches, check runs, and reviews changed since the last successful sync timestamp for each repository.
    
*   Soft sync updates the development information (PR status, linked work packages, check status) on the affected work packages.
    
*   Admins can trigger a hard sync manually from the GitHub integration admin settings on OpenProject side, either for all repositories or for a selected repository or project.
    
*   Hard sync ignores the last-sync timestamp and re-fetches all relevant GitHub data for the selected scope, then reconciles it with what OpenProject holds (adds missing items, updates stale ones, removes links to deleted PRs or branches).
    
*   Only one sync job runs per repository at a time. Overlapping soft and hard syncs are queued or skipped, and the admin is told when a hard sync is already running.
    
*   The admin UI shows, per repository: last successful sync time, sync type (soft or hard), status (success, partial, failed), and error details.
    
*   Failures on one repository do not block syncing of the others. Failed repositories are retried on the next scheduled run.
    
*   GitHub API rate limits are respected: the job backs off and resumes rather than failing, and the admin is warned if limits keep delaying syncs.
    
*   The hourly soft sync can be enabled or disabled, and its interval configured, by an admin.
    
*   Sync runs and outcomes are written to the audit or system log.
    

**Technical notes**

*   Feature reference from Jira DataCenter: [https://support.atlassian.com/jira/kb/how-the-dvcs-synchronization-works-in-jira-server-and-data-center/](https://support.atlassian.com/jira/kb/how-the-dvcs-synchronization-works-in-jira-server-and-data-center/)
    

**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_&nbsp;
    

**Out of scope**

*   <br>
    

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