Forums > Integrations & Plug-Ins > Bug Tracker Data-Sync Int... > Incident update and user ...
The synchronization only updates the incidents/issues in the direction JIRA > SpiraTest. For newly logged incidents/issues, the information can flow in either direction.
Therefore the recommended process is to have the tester close the issue in JIRA once they have completed the retest. Then the change will flow into SpiraTest on the synchronozation run. If you change the status of the incident directly in SpiraTest it will be overwritten by subsequent changes made in JIRA.
Data mapping is independent of the number of licenses so you only need to purchase enough licenses in SpiraTest for the QA team to login. This works because SpiraTest is licensed by number of concurrent users not number of total users.
results match your keyword(s)