---
sourceDocument: Zurich Strategic Portfolio Management
sourceDocumentLink: https://www.servicenow.com/docs/r/zurich/it-business-management

 Release :

    - zurich

ft:locale :

    - en-US

ft:publication_title :

    - Zurich Strategic Portfolio Management

ft:clusterId :

    - itbm

bundleId :

    - itbm

workflow :

    - Technology


---

# Reporting defects in Agile Development 2.0

# Reporting defects in Agile Development 2.0 {#ariaid-title1}

* Release version: Zurich
* 
* Updated August 11, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Create defects for the issues that are reported for your product using Agile Development 2.0. You can then create stories for these defects so that your teams can
start working on resolving them.

Defects can be used to report and track the resolution of issues that are noticed during the development of a new feature, or as feedback for existing features. Product owners then review these defects and decides on creating
stories for them, which are assigned to the relevant assignment groups.

## User role to create defects

Users who are expected to create defects in Agile Development 2.0 must have one of the following roles:

* feature_user
* scrum_story_creator
* scrum_admin
{#defect-reports__ul_nwq_fl5_3tb}

However, if a user has just the feature_user role, they can only view the defects from the
Defects module of the Agile Development application. They can not
view the stories associated with the defects in the Stories related list of the defect
record.

For information on how to create Defects, see [Report a defect in Agile Development 2.0](https://www.servicenow.com/docs/5c_D8nh_1Xa4FFXyZn7dXA "Track issues associated to your product or feature by reporting defects in Agile Development 2.0.").