20. JIRA Integration Enhancement
Why was this developed?
In the previous version of Avo Assure, based on the generated reports, Avo Assure users could log defects on JIRA using Avo Assure. Mapping was only possible with test cases. With the development made by the Avo Assure team, JIRA mapping is now possible with user stories.
How does it look?
![](https://docs.avoautomation.com/~gitbook/image?url=https%3A%2F%2F420146545-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FTb6M8zQCzQSmPAQyfnHz%252Fuploads%252FBy8orqWQUZbrXalrUxKR%252F0.jpeg%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=d8bf95db&sv=1)
How does it work?
The user has to click the Reports Plugin from the Avo Assure home page, and the Testing Reports window will be displayed.
![](https://docs.avoautomation.com/~gitbook/image?url=https%3A%2F%2F420146545-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FTb6M8zQCzQSmPAQyfnHz%252Fuploads%252Fo7ULF3MPxV3y1fO8N3ea%252F1.jpeg%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=8a611e91&sv=1)
The user has to click the Functional Test button, select the Project from the Project dropdown, and select the Batch/Module from the batch/module dropdown.
![](https://docs.avoautomation.com/~gitbook/image?url=https%3A%2F%2F420146545-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FTb6M8zQCzQSmPAQyfnHz%252Fuploads%252Fy0aafze1dhZDelsIBjv2%252F2.jpeg%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=c891daa0&sv=1)
Once the project and module are selected, Execution reports will be displayed. The user has to click the required Execution no and click the HTML view icon. The new Avo Assure Execution Report window will be displayed.
![](https://docs.avoautomation.com/~gitbook/image?url=https%3A%2F%2F420146545-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FTb6M8zQCzQSmPAQyfnHz%252Fuploads%252FPaXfdHV2kobZcWO5EYyQ%252F3.jpeg%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=1d2825a4&sv=1)
The user has to click the JIRA Login button and enter the JIRA login credentials. Click the Connect button.
![](https://docs.avoautomation.com/~gitbook/image?url=https%3A%2F%2F420146545-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FTb6M8zQCzQSmPAQyfnHz%252Fuploads%252FfK6wNpg7AnTE3gBjrIP1%252F4.jpeg%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=8b409fbc&sv=1)
The Log Defect will be enabled once the JIRA is connected. Click the Log Defect button.
![](https://docs.avoautomation.com/~gitbook/image?url=https%3A%2F%2F420146545-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FTb6M8zQCzQSmPAQyfnHz%252Fuploads%252FteTbbdkGG4Wg96HvVLMV%252F5.jpeg%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=dae907d3&sv=1)
The Create Issue window will be displayed with pre-filled data. The user has to enter the Environment field and click the Proceed button.
Once the defect is created, the Avo Assure Execution Report log defect will be changed to Jira Defect ID.
The user has to click on the Jira Defect ID. Jira Defect ID will navigate to Jira Software, and the user can view the Linked Issues.
How can I get this?
If the user upgrades to the latest version of Avo Assure to 23.1.0, this feature will be available automatically.
Last updated