Qt empowers productivity across the entire product development lifecycle, from UI design and software development to quality assurance and deployment. Find the solution that best suits your needs.
Get the latest resources, check out upcoming events, and see who’s innovating with Qt.
A wealth of Qt knowledge at your fingertips—discover your ideal learning resource or engage with the community.
Whether you're a beginner or a seasoned Qt pro, we have all the help and support you need to succeed.
Jira, originally designed solely as a bug and issue tracker, now serves agile development and QA teams for their project/product management, test and requirements management, defect tracking and release planning needs.
Jira integrates with Squish Test Center to automate the pushing of test results from Test Center to Jira, and allows for mapping of Jira issues to Squish test cases.
Jump between Squish Test Center and Jira through a seamless synchronization between the two systems.
With a push of a button, information from an Issue Ticket in Jira can be transferred to Test Center’s database. From there, you can map which Squish tests are associated with which Jira tickets. Test Center’s Overview page lists the Issue Tickets and the associated Test Status.
Tests uploaded to Squish Test Center can have their results pushed to Jira. The result of each case will automatically update the ticket’s State within Jira (e.g., Resolved/Unresolved).
These push and pull operations can be automated through a command line utility, such that results are pushed whenever new test results are uploaded to Test Center.
Mapping of Jira issues to Squish test cases allows for automated tasks to be performed within the Jira platform, including automatically opening a defect ticket in Jira if a test uploaded to Squish Test Center has failed.
Within the ‘Description’ section of the created ticket, a backlink to Test Center’s Explore page will appear which lists the failed test case and the test suite which contains the test.
Jira permits customized, or non-standard, workflow definitions. A benefit of custom workflows is that they can be configured to reflect your organization’s unique processes.
Test Center’s Jira integration handles non-standard workflows through an easy-to-define ‘Workflow’ field in the Integration’s settings page. There, you can define States and Transitions in agreement with your internal processes, which will be reflected when pushing results to Jira.
More information can be found in our documentation.