Testing and Fixing Bugs


JSU for Jira Server/Data Center

This is the documentation of JSU for Jira Server/Data Center. If you are using JSU on Jira Cloud, see our JSU for Jira Cloud documentation.

One of our most common use cases is with customers interconnecting the workflows of testers and developers to resolve bugs. This is illustrated in the workflow below.

How does JSU automate this workflow?

  1. When a test fails and the tester clicks the NOK (Not OK) transition, a new bug issue is created and linked to the test automatically. With every bug the tester finds, this process can be repeated and a new bug issue is created. See our Create Linked Issue post function to learn more.

  2. The test is automatically set to “Ready for Re-Test” after all the related bugs are fixed. The fix version is copied to the test so the testers know which version needs to be retested. See our Linked Transition Post Function to learn more.

  3. When a test passes and no bugs are found, the tester selects the Ok transition. All the linked bug issues which are now fixed, are closed automatically. See our Linked Transition Post Function to learn more.

Diagram of a relationship between a software testing workflow and a bug fixing workflow.