Create defects



The old navigation will be removed from Jira Align in early 2024.
Learn more about the upcoming changes

A defect is a condition in software which does not meet a software requirement or user expectations. Defects are used to identify differences between what is expected and what is actually produced. Create defects from any page with the Create button in the top navigation bar. Alternatively, create and manage defects from the defects page:

If you’re using the new navigation:

  1. Select Items in the top navigation bar.
  2. Select Defects; the defects page displays.


  1. Select Teams in the top navigation bar and select the team you want to view information about.
  2. On the sidebar, select More items in the list of options.
  3. Select Defects; the defects page displays, filtered by the selected team.

Note: This page supports filtering by portfolios, solutions, programs, or teams outside of your sidebar team selection.

If you’re using the old navigation:

  1. Select Team from the left Nav menu.
  2. Under the Team section, select Defects; the defects page displays.

To add a defect:

  1. On the defects page, select click the Add Defect button on the toolbar (top-right of the page). The New Defect slide-out panel displays.
  2. Type the defect's name in the Defect Title field.
  3. Select the defect's Priority, Severity, Status, and State from the corresponding drop-down menus.
  4. Select the program the defect belongs to from the Program drop-down menu.
    Note: If you’re using the Jira or Azure DevOps connector, the primary program assignment is locked in Jira Align after it's been set for an item and synced to Jira. To change the program assignment in Jira Align after the defect has been synced to Jira, you'll need to change the project assignment on the corresponding Jira issue or the area path assignment on the Azure DevOps item.
  5. The remaining fields on the New Defect panel are optional. Enter values for the following fields as needed:

    • Category: The category the defect belongs to.
    • Frequency: How frequently the defect occurs.
    • Program Increment: The program increment assigned to the defect.
    • Team: The team assigned to address the defect.
    • Assigned To: The user assigned as owner of the defect.
    • Fixed By: The user that fixed the defect.
    • Sprint: The sprint the defect belongs to.
    • Find Story: Enter the name, ID, or tag to search for the story the defect belongs to.
    • Story: The selected story the defect belongs to.
    • Description: A free-form description of the defect.
    • Steps To Reproduce: Free-form steps required to reproduce the defect.
    • Expected Results: Free-form expected results that should occur instead of the defect.
    • Actual Results: Free-form actual results that occur when attempting to reproduce the defect.
    • Fix Results: Free-form results of reproducing the defect after a fix is in place.
    • Notify: Users that will receive a notification about the defect.
    • Tags: Keywords that aid in the search for the defect.
    • Functional Area: The functional area the defect impacts.
    • Suite: The defect suite this particular defect belongs to.
    • Kanban Status: The kanban status of the defect, such as ready for testing or verified.
    • Release Vehicle: The release vehicle this defect belongs to.
    • Version: The version of the product this defect belongs to.
    • Database: The database in use when the defect was found.
    • OS Client: The client operating system in use when the defect was found.
    • OS Server: The server operating system in use when the defect was found.
    • Blocked: Identify if the defect is blocked; free-form field to enter additional comments.
    • Duplicate of: Identify if the defect is a duplicate of another defect; free-form field to enter additional comments.
    • From Customer: Identify if the defect was reported by a customer.
    • Commercialize: Identify if the defect should be made visible to customers or reported in release notes.
    • PM Reviewed: Signify if the Product Manager has reviewed the defect.
    • Affects Doc: Signify if the defect impacts documentation, such as user guides or online Help.
    • Estimate: Three fields to enter estimated Points, Hours, and Remaining hours to fix the defect.

  6. Click Save. The defect is added to the defects page.  


Was this article helpful?
0 out of 0 found this helpful
Print Friendly Version of this pagePrint Get a PDF version of this webpagePDF

Join the Atlassian Community!

The Atlassian Community is a unique, highly collaborative space where customers and Atlassians come together. Ask questions and get answers, start discussions, and collaborate with thousands of other Jira Align customers. Visit the Jira Align Community Collection today.

Need to contact Jira Align Support? Please open a support request.