Here are some troubleshooting tips for some common questions about requirement synchronization with JIRA.
- When Synchronizing from JIRA to Enterprise Tester no requirements are created.
If nothing is synchronized from JIRA to Enterprise Tester, but no errors are displayed, check to make sure that on the External System Configuration tab you have selected all the issue types you wish to synchronize.
- The type of a synchronized requirement is changed in Enterprise Tester, but it did not change in JIRA
Changing an issue from one type to another with mapping statuses etc. is not currently supported from Enterprise Tester to JIRA. This change will cause an error to occur and the synchronization of the entity in question will fail. You can either stop mapping Type or change the Type back to its old value (this could also be achieved by just performing a full sync in the direction of External System -> Enterprise Tester).
- Why can't I add comments via the Requirements screen?
Comments on Requirements and Scripts are not supported. Displaying comments from external systems (such as JIRA) on the requirements screen is supported once the Requirement has been synchronized with JIRA.
- Why am I getting duplicate requirements created?
If more than one requirement link is set up per project, duplicate requirements may be created. If the requirement matches the synchronization filter criteria of more than one requirement project link your requirement will be imported by each of these links. The only way to avoid this is to define your filter criteria to exclude these entities.