---
title: "Testing and fixing bugs"
canonical: "https://support.appfire.com/space/JSU/12682117/Testing%20and%20fixing%20bugs"
format: markdown
---
> Macro (aura-html)

> ℹ️ This content is for JSU for Jira Server/Data Center. If you are using JSU on Jira Cloud, see our JSU Cloud [documentation](https://appfire.atlassian.net/wiki/spaces/JSUCLOUD/pages/12518446).

One of our most common use cases involves customers interconnecting the workflows of testers and developers to resolve bugs. The workflow below illustrates this.

## 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.** This process can be repeated for every bug the tester finds, and a new bug issue is created. See our [Create Linked Issue](https://appfire.atlassian.net/wiki/spaces/JSU/pages/12682165) post function to learn more.
2. After all the related bugs are fixed, the test is automatically set to *Ready for Re-Test*. The fix version is copied to the test so the testers know which version needs to be retested. See our [Linked Transition](https://appfire.atlassian.net/wiki/spaces/JSU/pages/12682197) 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 that are now fixed are closed automatically. See our [Linked Transition](https://appfire.atlassian.net/wiki/spaces/JSU/pages/12682197) post function to learn more.

![Diagram of a relationship between a software testing workflow and a bug fixing workflow.](media://0af6cf09-0b41-4545-8be8-cec205ccfef6)