Synchronization modes - overview

The way your data flows depends entirely on the Sync Mode configured in your Spira plugin settings. The following options are available:

  • Default (Leave Blank): Recommended for most teams where QA works in Spira and Dev works in Jira. Requirements flow one-way from Jira to Spira. Incidents log from Spira to Jira, but subsequent updates sync back from Jira to Spira.

  • Bidirectional: Similar to Default, but Incidents fully sync both ways for both new creations and updates.

  • Complete (Jira Cloud only): Full bidirectional creation and updates for all supported artifacts (Releases, Requirements, Incidents, and Tasks).

  • NoRequirements: Syncs only Incidents and Tasks. Requirements are ignored.

  • NoIncidents: Focuses entirely on Requirements and Tasks. Incidents are ignored.

Important Workflow Note: For any artifact configured for one-way synchronization (e.g., Jira → Spira), any changes made directly inside Spira will be overwritten and lost on the next synchronization cycle.

What Synchronizes Between Spira and Jira

  • Incidents

    • Spira incidents are synchronized in Jira as bugs

    • Jira bugs are synchronized in Spira as incidents

      • In Default Mode: New incidents sync from Spira to Jira. Any changes made in Jira after synchronization are applied back to Spira, but changes made in Spira after synchronization will be overwritten by Jira.

      • In Bidirectional or Complete Mode: Changes made to an incident/bug in either system will safely sync both ways.

  • Releases

    • Existing releases in Spira or Jira are synchronized, only if they are assigned to an item (before Jira plugin v8.0 or earlier. Starting from datasync v8.0 releases syncing bidirectionally with no need for artifact association). 

      • 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.

      • In Default / Bidirectional Modes: Requirements flow one-way (Jira →​​​​ Spira). Requirements created or updated in Spira do NOT synchronize back to Jira.

      • In Complete Mode (Jira Cloud only): Requirements sync fully bidirectionally.

    • Hierarchy/Epics:

      • Jira Cloud: Supports syncing the full Epic →​​​​ Story hierarchy structure.

      • Jira Server/DataCenter: Requirement hierarchies are not synchronized due to architectural differences.

  • 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

    • In Default / Bidirectional Modes: Any changes made to those Tasks in Jira after synchronization are applied in Spira, but any changes made in Spira after synchronization are lost (overwritten on the next sync).

    • In Complete Mode (Jira Cloud only): Tasks sync fully bidirectionally.

  • 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

    • Make sure both Jira and Spira are operating in the same timezone. If they are not, you must adjust the Time Offset value on the plugin configuration page so updates and comments sync correctly (use Spira as the baseline: if Jira is 2 hours behind Spira, enter 2,  if Jira is 2 hours ahead, enter -2 ).

    • Comments: Synced bidirectionally by default between Spira and Jira. This can be optionally disabled in your data sync configuration settings.

    • Attachments:

      • Jira Cloud: Dynamically synchronized when items are created and whenever they are updated.

      • Jira Server/DataCenter: Synchronized during initial creation only. They do not sync during subsequent updates.

      • Disabling Attachments: You can block all attachment syncing by adding ,NoAttachments to your Sync Mode setting.

    • Tags: Spira artifact tags sync seamlessly as Jira labels, and vice-versa.

    • Users: Users are not dynamically created. Jira users must be mapped to existing Spira users via manual mapping or by enabling the "Auto-Map Users" configuration option.

Combining Modifier Parameters

If you want to use special parameters like NoAttachments or createReleasesOnly, append them directly after your main Sync Mode with a comma and no spaces.

  • Example: Complete,NoAttachments,createReleasesOnly

  • Example: Bidirectional,createReleasesOnly