QAComplete seamlessly integrates with JIRA – the QAComplete Integration for JIRA plugin enables synchronization between JIRA issues and QAComplete defects and requirements.
To synchronize items:
While the synchronization is enabled, when you update an item in one system, the corresponding item will be updated in another system automatically. The synchronization is real-time. Changes you made to an item in one system are copied to another system immediately.
During the initial setup, you can decide whether you want to synchronize the existing QAComplete and JIRA items created before the synchronization was enabled. It is also possible to synchronize the existing items at any time, on the JIRA plugin configuration screen in QAComplete:
When you add a comment (note) to an item, the comment (note) will be copied to the corresponding item in another system. The information on the comment’s (note’s) author will be copied as well. When you attach a file to an item in one system, the attachment will be automatically copied to the corresponding item in another system. When you update the attachment in one system, the corresponding attachment will be updated in another system (if the attachment names coincide).
All actions applied to synchronized items by you and other users are stored in QAComplete as log records.
In QAComplete, synchronized items have the Synced label in the Edit form and a link to the corresponding JIRA issue:
In JIRA, synchronized issues have a link to the corresponding QAComplete defect or requirement:
Click the link to open the corresponding item.
|Note:||If you change the type of a JIRA item (for example, move it from Bug to Story), QAComplete items synchronized with it will not change their type.|
Currently, JIRA items of the Sub Task type cannot be synchronized with QAComplete items.
The cross-referencing links between items are not synchronized. For example, if a JIRA issue has links to other JIRA issues, those links will not be copied to the appropriate QAComplete item.
When you create a new item (for example, a Task) in JIRA, the appropriate item (Requirement) will be created in QAComplete.
Based on the created QAComplete item, items of the appropriate types (Story and Epic) will be created in JIRA.
The QAComplete item will contain links to all JIRA items with which it is synchronized.
In JIRA, it is possible to apply the wiki-style markup to text in item fields. Some of these tags are not supported in QAComplete. Please check the table in the section below for reference.
||Hyperlinks without inner text|
When working with QAComplete and with the synchronized JIRA instance, and when moving items from one project to another, please take into account the following behavior:
When you delete a synchronized item from a JIRA project, the QAComplete item will be deleted as well.
When you move an item from a non-synchronized JIRA project to a synchronized JIRA project, a new connected item will be created in QAComplete.
When you move an item from a synchronized JIRA project to another JIRA project, the connected QAComplete item will be removed.
If the JIRA project that stores the item after the transfer is integrated with another QAComplete project, a new item will be created. It will be identical to the deleted item, but there will be no history of changes.
On the > Integrations page, you can prepare and configure your integration, and view the current state of the connection between your QAComplete and JIRA instances.
If you are logged in as a user with no specific permissions, you can view the current state of the connection, the URL of your JIRA instance, and the time the items were last synchronized in QAComplete and JIRA. To configure the connection, contact your security administrator.
The plugin supports QAComplete version 11.3 and later.
If you have an earlier version of QAComplete, you will have to use the QAComplete - JIRA Connector standalone service to synchronize items. In this case, please contact our Support Team.