Synchronization Details
The following table (thanks Mark Grossman for your help) lists what synchronizes:
Gitlab ItemType:Field | SpiraTeam ItemType:Field | Sync behaviour (after initial sync) | Comment |
|---|
Issue:Description | Incident:Description | One-way: Gitlab -> Spira | Read-only in SpiraTeam after initial sync |
Issue:Title | Incident:Name | One-way: Gitlab -> Spira | Read-only in SpiraTeam after initial sync |
Issue:Status | Incident:Status | Two-way sync | |
Issue:Comment | Incident:Comment | Two-way sync | Comments from one side will be added to the comment flow of the other. Updates to existing GitLab comments are not synched. |
Issue: Creator | Incident: Opener | One-way: Gitlab -> Spira | Read-only in SpiraTeam after initial sync. When you create a new incident in SpiraTeam, the creator in GitLab is always set to the synchronization user. |
Issue: Assignee | Incident: Owner | One-way: Gitlab -> Spira | Read-only in SpiraTeam after initial sync |
Issue:Milestone | Incident:Resolved Release | One-way: Gitlab -> Spira | |
Milestone: Name | Release: Release Name | No longer synced | No longer synced after initial sync. Fields may be changed in both. However, note Milestone Object/Release object link is still maintained. |
Milestone object | Release object | Linked by Gitlab ID, remains synced for use by Detected Release, Resolved Release and Verified Release |
Using a GitLab "Guest User"
- A GitLab guest user has full control over their OWN created issues i.e. they can Open new issues, Close those issues, and set them to Open again. This is great for all QA issues that originate from SpiraTeam and get added to GitLab
- However, a Guest user cannot set to Open or Closed issues where they are not the Creator. Therefore if you set an issue created by someone else (e.g. a Dev from within GitLab) to Reopen from SpiraTeam (which would typically be mapped to Gitlab Open) that on the GitLab side it is not set to Open.
- So if you use a "guest" user as the synchronization user, the synchronization will need to be limited to one-direction only