Retrieve Requirements

Keep all your JIRA issues in JIRA with synced instances in qTest:

  • Get all or selected JIRA issues of any type (Story, New Feature, Enhancement, Etc.) as qTest requirements
  • Retrieved requirements have both qTest and JIRA properties
  • JIRA requirements are read only in qTest to prevent accidental updates
  • Retrieved requirements have both qTest and JIRA properties

Manage Requirements

Organize, Create test cases and link to JIRA issues:

  • Move or Copy imported requirements within qTest modules
  • Real-time updates to JIRA imported issues
  • Associate qTest Test objects to requirements
  • Link qTest objects to JIRA requirements to generate JIRA links

Requirements Reporting

Take advantage of qTest’s robust reporting capabilities:

  • JIRA IDs of imported issues included in requirements and test execution status reports
  • JIRA widget for ready-to-view integration summary from the JIRA project
  • Generate coverage and rest run reports on JIRA retrieved requirements from qTest

Easy Setup

Integrate qTest with JIRA cloud or Server and easily submit defects to JIRA as well as import requirements to from JIRA. Setting up and getting started with qTest — JIRA integration is as easy as 1,2,3

  • JIRA

    Integrates with both JIRA Cloud and Server version

  • Configuration

    One time configuration that is saved automatically

  • Connection

    Activate/deactivate connection through ON and OFF switch anytime


Centralized Defect Tracking in JIRA

Defects are no longer all over the place. Submit defects directly into JIRA from qTest:

  • Direct defect logging into JIRA project through qTest
  • Test execution report defects during or after a test run
  • Auto-fill defect fields as configured link back to the Test
  • Run from JIRA linked defect’s page

qTests Built-in JIRA Widget

Get the summary of a qTest project and a JIRA project integration right from your JIRA instance:

  • Install qTest for JIRA Cloud for integration summary
  • View real-time defect and requirement coverage and resolution analytics
  • Export the reports to Excel for further processing

About JIRA Requirements

Many organizations house their “requirements” in JIRA as items known as JIRA issues.  Often, many call JIRA issues Epics, stories, tasks, sub-tasks, or custom issues they have.  Regardless of how they can be classified, qTest can pull in any JIRA issue type.  This grants testers with the ability to create test cases off these and in addition, the dev team and/or business admins can see these associated test cases on the JIRA end.

Frequently Asked Questions about JIRA Requirement with qTest:

  1. Can I display custom JIRA fields in the view?
    Yes, you can set this up within the integration settings area by clicking on the wrench next to the issue type you are pulling over.
  2. Can I add multiple JIRA projects to a single qTest project?
    Yes, you can submit defects to multiple JIRA projects and/or pull in requirements from multiple projects too.  This is done within the Integration Settings area in qTest.
  3. Can I edit the JIRA fields from within qTest?
    No, the JIRA fields are not editable from qTest.  We want JIRA to remain as your source of truth and wouldn’t want testers modifying requirements.  This also avoids data collision issues.
  4. What type of sync do I have to setup to move the data between the two systems?
    No sync or scheduled job is required to move changes in the artifacts between the tools.  We achieve the real time integration by utilizing the JIRA webhooks, which are more of event based driven changes opposed to a full on database sync.
  5. We house our requirements in Confluence, how can I get them into the tool?
    This is actually not a recommended practice by Atlasssian, this would be similar to housing requirements in Google Docs.  Anyone can edit them, no versioning, etc. If you must, you can create a custom field (within qTest) with a URL type and then populate that to link to the confluence requirement.

Get Started with qTest