TestRail and Jira Integration 101

TestRail and Jira two-way integration can help your team speed up testing, improve communication, and identify risky releases.
Learn how to link test results to issues, create bug reports in Jira directly from TestRail, and run powerful coverage reports. Look up issue details and jump to Jira to test results within Jira issues.
Check out this full step-by-step tutorial to see how you can easily integrate TestRail with Jira and efficiently manage, track, and coordinate your software testing efforts - all from a centralized and easy-to-use web application.
You'll learn about:
00:00 - How To Set Up the Integration in TestRail
04:00 - Configuring the Defects Integration
08:08 - Pushing a Bug to Jira Directly from TestRail
12:28 - Configuring the References Integration
14:08 - Setting Up Traceability with TestRail and Jira
17:03 - Checking Test Coverage with Reports
22:01 - How To Configure the TestRail Jira App
23:57 - Monitoring Test Progress Inside Jira
📢 Make Your Testing More Efficient with the TestRail Academy
academy.testrail.com/
Get in touch!
[e-mail]
Connect with us on LinkedIn
/ testrail 👈
Follow us on Facebook
/ testrailbygurock 👈
Follow us on Twitter
/ testrail 👈

[@BettSwinger]

Without having tried to configure the integration from scratch in parallel with the video, I have to say that this is a very well and understandably explained video. Thanks for that, Diogo! However, I still have some comments on usability and improvements: 7:41 Why are there 3 Fields with the name "Steps" in the "Add Fields" list? Whats the difference between those 3? You should really finally change the name to someting more readable so users don't have to select each one to find the correct one needed. We stumble across it ourselves on a regular basis. Quite annoying. Additionally: TestRail and Jira use a different markdown syntax. This leads to the following problem: If you configure the placeholder for "Steps" in the description, the Markdown formatting from TestRail is retained when pushing. The Jira ticket is then incorrectly formatted and requires very time-consuming manual rework. In my opinion, the TestRail Markdown should be automatically converted to Jira Markdown. 10:26 & 15:23 The hover preview would be more readable for the user if the text formatting was taken from Jira instead of displaying Markdown text. When we push Step informations from TestRail to Jira, the systems use different markdown formatting. I also miss a push function that doesn't create the ticket directly, but first (comparable to the "Add" function), opens the Add Bug dialog of Jira where all the information from the configuration is already automatically inserted / filled. I'd like to have a preview in Jira BEFORE creating the ticket and if necessary be able to manual do corrections, such as formatting changes with the much more comfortable Jira Editor, instead of having to edit everything in the uncomfortable, tiny and rudimentary TestRail Push Dialog. 14:55 & 16:45 It would be very helpful to be offered autocomplete based on Jira ticket number or Jira title for references. (Same by the way also when adding a defect). 19:51 & 20:35 Why is there such an ugly early 2000s design break in the charting here compared to other charts within TestRail? (for comparison see e.g. 26:59). Also: Do the charts in reports take into account the chart themes that can be customized in the admin area? 21:47 Isn't the hover preview missing here? 24:42 It would be helpful if there was a free text field to type in to filter the selection to make it easier to find a project.

[@testrail]

Hi there! Thank you so much for sharing your experiences with TestRail-we are beyond appreciative for all of your thoughtful and detailed feedback. We are always looking to improve the TestRail experience, and you have some great ideas for how to streamline usability with the TestRail Jira integration. Feel free to submit feedback and feature requests directly to our product team for their consideration at support.testrail.com/hc/en-us/requests/new?ticket_form_id=7738788856596. Thank you so much again!

[@diegoelet]

That minute 25:50 Left me with 2 questions. 1- What happens on TestRail when the tester is trying to ReExecute again after the previous reported bug is fixed? A new Execution log(displaying the new day) is started OR is the same as Xray by just continuing the original execution(first execution) ? 2-Does TestRail plugin support this ? kzbin.info/www/bejne/bWPHl2h8q82kZsk " Integrating Test Automation and Test Management with Zephyr for Jira " Thank you for this helpful video :)

[@testrail]

Thank you for reaching out! In the scenario that a linked defect is closed/fixed, the "reference" field within the TestRail test case will maintain the defect identifier. Maintaining this linkage of defect/issue to your agile defect tracker is considered a best practice for traceability and test quality of record. See more detailed information around defect integrations here: support.testrail.com/hc/en-us/articles/7747333895700-Introduction-to-reference-and-defect-integrations TestRail does have a supporting App that complements the Jira integration. See configuration and features here: support.testrail.com/hc/en-us/articles/7746958913940-TestRail-Jira-App

[@karolwololo6826]

Can we get the results while the Jira ticket is loading to avoid clicking the show button? kzbin.info/www/bejne/h3qlfIJ7jb91e5Isi=ehf31nKZ2uJavKfV&t=1503