What’s New in the Jira Cloud Integration
We’ve re-engineered our Jira Cloud sync engine to simplify configuration, improve data fidelity, and support deeper collaboration across your teams.
- Automated Implicit Data Mapping: One of the most important tasks when using the data synchronization is to map the fields and field values between Jira and Spira to ensure smooth synchronization of data. This can be time consuming, so to massively speed things up, if the values of the field are the same in Jira and Spira, mapping will no longer be needed. Instead you'll only need to map values when they are different between the two systems!!
- Complete Sync Mode: System administrators will be able to configure the Jira dataSync plugin to use a new Complete sync mode, so all the supported artifact types can sync bidirectionally between Jira and Spira:
- Requirements
- Incidents
- Tasks
- Releases
- Requirements Hierarchy: There will be an option to synchronize the Requirements hierarchy between Jira and Spira. This means that the Epic > Feature > Story hierarchy in Jira will be reflected in Spira as a hierarchy of requirements (and vice-versa).
- Attachments Synchronization: Previously the integration would copy across the attachments when a requirement, task or incident was first created, but not synchronize any additional attachments after that. This meant that the attachments list would become stale. There is now the option to enable full synchronization of attachments whenever the associated artifact is updated in either system.
- Enhanced Rich Text Handling: We have improved the handling of rich text handling between the two systems so that you can still enjoy the benefits of bidirectional synchronization while keeping your original text formatting.
- Releases Sync: Previously the integration would create new Releases in either system but would not sync them after the initial creation. Now the sync will update the following fields:
- Name
- Description
- Start Date
- End Date
- Released flag
- Archived flag
- Releases Custom Field: Now custom fields on requirements, tasks and incidents of type Release will be synchronized.
- Status Multiple-Value Sync: For those artifacts where the the statuses are not customizable, allow the sync of multiple Jira statuses to one Spira status (as well as the reverse which was already possible).
- More Control Over What Syncs:
- You can configure the integration to not sync any comments
- You can configure the integration to ignore certain Jira issue types.
Frequently Asked Questions (FAQs)
- Will this new synchronization be available for all editions of Spira?
Yes, this functionality will be available for SpiraTest, SpiraTeam, and SpiraPlan. However some aspects will not be applicable to SpiraTest since it doesn't have support for Tasks.
- Will this new synchronization be available for both the Cloud and On-Premise versions of Spira?
Yes, this functionality will be available for all Spira customers, regardless of whether they are self-hosted or hosted by Inflectra SaaS.
- Will this new synchronization be available for both the Cloud and On-Premise versions of Jira?
No, this functionality is only for the Atlassian Cloud (SaaS) version of Jira. We are not extending these enhancements to our Jira Server / DataCenter integration. This is because Atlassian has been prioritizing its Cloud platform and therefore it didn't make sense to update the Server / DataCenter plugin. That being said, we still provide and support the plugin for Jira DataCenter and Jira Server.
New Confluence Integration
In addition to these enhancements to our Jira synchronization we will be releasing an official SpiraApp for connecting Spira to Atlassian Confluence. This new plugin will be based on the great community plugin created by our very own Dermot Canniffe.
This SpiraApp enhances Spira Requirements by adding a dedicated "Confluence" button to the Requirement details page toolbar. This button provides a streamlined workflow for linking Spira Requirements to Confluence pages:
- Open Existing Link: If a Confluence page URL is already present in a pre-configured custom field on the Requirement, clicking the button will open this URL directly in a new browser tab.
- Create New Page & Link: If the configured custom field is empty or does not contain a valid URL:
- A new page will be created in a designated Confluence space via the Confluence API.
- This new Confluence page will automatically include a link back to the originating Spira Requirement (showing its name and ID).
- The URL of this newly created Confluence page will be populated into the configured custom field on the Spira Requirement form.
- The newly created Confluence page will then open in a new browser tab for immediate viewing or editing.
- Crucial User Action: After the link is populated into the Spira form, the user must manually click Spira's main "Save" button on the Requirement details page to persist this new Confluence link.
What’s Next?
This is more than a product update—we are reimagining how Spira connects your tools, teams, and workflows.
If you're ready to streamline traceability, eliminate data silos, and supercharge collaboration across Jira and Confluence…
Join our early access program today and be the first to test these new features before the public release! Contact us today!