Checking the Configuration
Firstly, make sure that you have read the Spira External Bug-Tracking Integration Guide. This manual describes the different options for data synchronization (whether cloud-based or on-premise) and has a dedicated section in the manual for each bug-tracker, including:
- Jira
- Bugzilla
- Mantis
- Axosoft
- Microsoft TFS
- Rational ClearQuest
- Rational Team Concert
- Redmine
Troubleshooting Steps
Assuming that you have followed all the steps in the configuration, the next thing to do is follow these troubleshooting steps so that when you log a support ticket with Inflectra, you have all of the necessary information:
- Clear the Event Log in SpiraTest (cloud) or Windows Event Viewer > Application Log (on-premise)
- Log a new incident in SpiraTest, it should appear in Jira
- Wait 5 minutes*
- Change the status of the incident to something else in Jira
- Wait 5 minutes*
- Does the change to the incident appear in SpiraTest?
- If not, is there an error? If so, please copy it and sent it to Inflectra Support.
- If it does update, it is working.
- If it doesn't update, click Force Resync in SpiraTest
- Wait 5 minutes*
- Does the change to the incident appear in SpiraTest?
- If not, is there an error? If so, please copy it and sent it to Inflectra Support.
*If you have set the polling interval to a larger value, you may need to wait more than 5 minutes.
How to Report the Error Messages
For errors in the Spira Event Log, you can just cut and paste the text into the support ticket.
If you are an on-premise customer, saving the entire event log as an .EVT or .EVTX format file, zipping it up and emailing it to us is best.