What Synchronizes Between Spira and Jira

  • Incidents
    • Spira incidents are synchronized in Jira as bugs
    • Jira bugs are synchronized in Spira as incidents
      •  any change made in Jira after synchronization are applied in Spira
      • BUT any change made in Spira after synchronization is lost (overwritten on next sync by what exists in Jira)
      • Unless you enable bidirectional synchronization mode
  • Releases
    • Existing releases in Spira or Jira are synchronized, only if they are assigned to an item
      • in a bug:
        • Detected Release --> "affects version"
        • Resolved Release --> "fix version"
      • in a requirement:
        • Release --> fix version"
  • Requirements
    • A Story in Jira is synchronized as a Requirement of type "User Story" in Spira according to the mapping defined.
    • Requirements in Jira are synchronized to Spira
    • Requirements in Spira are NOT synchronized to Jira
  • Tasks
    • A Task in Spira is synchronized as a Sub-Task in Jira according to the mapping defined.
    • New Tasks in Spira are synchronized to Jira
    •  any change made to those Tasks in Jira after synchronization are applied in Spira
    • BUT any change made in Spira after synchronization is lost (overwritten on next sync by what exists in Jira)
    • New Tasks in Jira are NOT synchronized to Spira
  • Other
    • An Epic in Jira won't be synchronized in Spira unless you add it as a requirement type and map it
    • A Build in Spira won't be synchronized in Jira, but it can synchronize from Jenkins or Bamboo