Creating a Defect from an Issue

Issues, which are usually reported from an external source, can be used as the basis for a defect, which are usually internal to your company. If you were not the person who created the issue, you need the Issue Manager or Analyst role to perform this function.

Required access roles:

  • App-specific: Defect Engineer
  • Baseline: Author

To create a defect from an issue, you can either start with the top bar then search for the needed issue, or you can start from the properties page of the needed issue.

  1. Do one of the following:
    1. From the global menu, click > Defect Management > Create Defect from Issue.
    2. Use the search page to locate the needed issue and click Submit. See About Searches.

    Or:

    1. Open the issue. See Opening an Issue.
    2. In the navigation pane, select Resolved By.
    3. Select Actions > Create Defect from Issue .

    The Create Defect page opens with the name of the model version against which the issue was created entered in the Reported Against Model Version field. Defect Management populates these fields based on the issue:

    • Priority
    • Description
  2. Enter these details:

    Field NameDescription
    Basics:
    Title Enter a title that briefly defines the defect.
    StateChoose the state the defect should be set to once created:

    StateDescription
    SubmitYou still need to gather additional details for the defect, but you want to enter the information you currently have.
    EvaluateYou will enter all the needed details and the defect is ready for assessment once you click Done.

    Expected Completion DateThe date when all associated defect actions are complete and verified.
    Reported Against Model Version Shows the model version the Issue was created against, if any. Click the ellipsis button to change if needed.
    Introduced In Click the ellipsis button to select the first revision of the model version where the defect is thought to exist.
    Reporting Organization By default, shows the organization associated with you (the person reporting the defect). Click the ellipsis button to select a different organization.
    When Found Select an option from the drop-down menu to indicate the stage of the model version development process where the defect was discovered:
    • Development
    • First Pass Test
    • Second Pass Test
    • Final Qualification
    • After Release
    • N/A
    Type For information only: shows the object type used to save the defect; cannot be changed.
    Policy For information only: shows the policy used to govern the defect; cannot be changed.
    Details:
    Severity Select the option that indicates how severe the defect is, where S0 is a showstopper and S3 is the least severe.
    Priority Select the option that indicates the priority for fixing this defect, where P0 means the highest priority and P3 is the lowest priority.
    Description Enter a detailed description of the defect.
    Steps to Reproduce Enter a step-by-step procedure showing exactly how to reproduce the defect.
    Environment Click the ellipsis button to select the environment (client and server operating systems, browsers, and so on) in use when the defect was discovered.
    Summary:
    Regression Select Yes or No.
    Regression From If regression is Yes, click the ellipsis button to select the model version revision where the feature last worked.
    Regression Details Enter a detailed description of the change that broke the relevant feature.
    NotesUse this field to enter discussion notes about the defect.
    Subscribers Click the ellipsis button to select people and member lists to be notified whenever a change is made to this defect.
    Keywords Enter a list of terms relevant to this defect that people can use when searching for defects.

  3. Click Done.