When you use SpiraTest with GitLab, the synchronization plugin synchronizes some fields unidirectionally and other fields bidirectionally. To clarify the details, this article illustrates which fields are synched and in which directions.

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.

Issue: Creator

Incident: Opener

One-way: Gitlab -> Spira

Read-only in SpiraTeam after initial sync

Issue: Assignee

Incident: Owner

Two-way 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

 

Article Info
  • Last Updated: 12/7/2018
  • Article ID: KB414
  • Views: 16