Viewing Defect Action Details

Click the Name of the Defect Action.

Note: The tool exports all fields on the Properties page except the Notes field because of its potential size.

This page lists these details:

Basics

• Name.The name for the Defect Action, which matches the name of the Defect.
• Originated. The date the Defect Action was created.
• Defect. The name of the Defect. Click to view the Defect's Properties page. See Viewing Defect Details.
• Defect Title. Copied from the Defect, shows the Defect's Title.
• Defect Action Description. A detailed description of the Defect Action.
• Defect Action Type. The area where the fix needs to be made.
  
  • Software
  • Hardware
  • Documentation
  • Test
• State. The lifecycle of the Defect Action showing the current lifecycle highlighted in yellow.
• Defect Reported Against Product. Copied from the Defect, shows the value of the Reported Against Product field. Click the name to view the properties page for the Product.
• Defect Introduced In. Copied from the Defect, shows the version number of the Product, Requirement, or other object affected by the Defect. Click the name to view the Properties page for the object.
• Committed for Product. If the Defect Action is committed for fixing in a Product (Actions > Commit for Product), that Product shows here. Click to view the Product's Properties page.
• Candidate for Model. If the Defect Action is connected to a Model as a candidate for a future release(Actions > Commit for Product), that Model shows here. Click to view the Model's Properties page.
• Satisfied by Build. If the Defect Action fix is planned for a specific build (Actions > Mark as Available in Build), that Build shows here. Click to view the Build's Properties page.
• Type. The ENOVIA object type used to save the Defect Action.
• Policy.The ENOVIA policy used to govern the Defect Action's lifecycle.

Ownership

• Action Assignee. The person assigned to performing the action defined by this Defect Action.
• Quality Assignee. The quality assurance person responsible for testing the fix implemented by this Defect Action.
• Subscribers. The people to be notified whenever a change is made to this Defect Action. The list of subscribers for a Defect Action includes the subscribers for the Defect, plus any people added to the Defect Action.
• Owner. The Development Manager who is responsible for the Defect.

Defect Details

• Severity. How severe the defect is, where S0 is a showstopper and S3 is the lease severe.
• Priority.The priority for fixing this defect, where P0 means the highest priority and P3 is the lowest priority.
• Description. A detailed description of the defect.
• Steps to Reproduce. A step-by-step procedure showing exactly how to reproduce the defect.
• Environment. The environment (client and server operating systems, browsers, and so on) where the defect occurred. Click the name to view the Environment's properties page.
• Regression. Yes or No.
• Regression From. If Regression is Yes, indicates in which version the feature worked.
• Regression Details. If Regression is Yes, detailed description about the regression.
• Keywords. A list of terms relevant to the Defect that people can use when searching for defects.

Defect Action Details

• Resolution.
  
  • Code Change.
  • Design Change.
  • Documentation Change.
  • N/A
  • Test Change
  • Workaround.
  • Waiver.
• Cause.
  
  • Always been there.
  • Bad bug fix.
  • Business Reason.
  • Configuration.
  • Context Handling.
  • Other.
• Where Found.
  
  • Netlist
  • Hardware
  • Software
  • Other
• Reason for Rejection. Only shows if the Defect Action was rejected. Lists the reason why the Defect Action was not accepted.
• Reason for Demotion. Only shows if the Defect Action was demoted from a later state to an earlier state.
• Notes. Any Resolution Notes entered when the Defect Action was promoted to test.

Dependent Actions. A list of other Defect Actions that rely on the resolution of this Defect Action before they can proceed.Dependent Actions. See Managing Defect Actions.

Implementation Reviews. A list of reviews defined for this Defect Action. See Managing Implementation Reviews.

Affected Items. A list of objects that are affected by the Defect Action.

Use the page Actions menu to work with the Defect Action. Commands only show when that action is available for the current lifecycle state of the Defect Action.

• Edit Details. Edits the details of the Defect Action. Any fields copied from the Defect cannot be edited on this page. See Editing Defect Action Details.
• Initiate Implementation Review. See Initiating an Implementation Review.
• Mark as Candidate. Opens a search page to select a Model to add this Defect Action as a candidate. If you select a Model, any Product that had previously been selected as "Committed for Product" is changed to a Deferral and shows on the Deferrals category.
• Commit for Product. Opens a search page to select a Product to indicate that the work defined by this Defect Action will be incorporated into that Product revision. Any previously selected Products are changed to Deferrals, and any Model selected by "Mark as Candidate" is removed.
• Mark as Available in Build. Opens a search page to select a build of the committed product to specify that the work defined by this Defect Action will be available in that build. If no product has been defined as committed, this action does not show.
• Add Affected Item. Opens a search page to select objects other than the original Product that the Defect was reported against that will be affected by the fix. The selected objects show in the Affected Items category for the Defect Action.
• Assign. Selects a person responsible for resolving and testing the Defect Action. See Assigning a Defect Action.
• Add Existing Dependent. Opens a search page to select an existing Defect Action to define it as dependent on this Defect Action. See Searching for Defect Actions. The selected Defect Action is listed in the Dependent Defect Actions category.
• Mark As Dependent of. Opens a search page to select an existing Defect Action to define that this Defect Action depends on the selected Defect Action's fix. See Searching for Defect Actions. This Defect Action is listed in the Dependent Defect Actions category of the selected Defect Action.
• Subscribe. Subscribe to notification for events that occur for this Defect Action. SeeSubscription Events for Defects and Defect Actions.

Use the page toolbar to promote or demote the Defect Action. Commands only show when that action is available for the current lifecycle state of the Defect Action.

• Promote to Open. When the Defect Action is in the Evaluate state, promotes it to the Open state and work should begin. See Opening a Defect Action.
• Demote to Open. When a Defect Action is in the Test, Closed, or Rejected state, demotes the Defect Action back to the Open state so the Action Assignee can work on it. See Demoting a Defect Action.
• Promote to Test. In the Evaluate or Open state, if the actions defined by the Defect Action have been completed and it is ready for testing, promotes the Defect Action to the Test state. See Testing a Defect Action.
• Demote to Test. In the Closed state, demotes the Defect Action to Test to indicate that additional testing needs to be done. See Demoting a Defect Action.
• Demote to Evaluate. In the Open, Test, Closed, or Rejected state, demotes the Defect action to the Evaluate state for more information. Demoting a Defect Action.
• Promote to Closed. In the Test state, promotes the Defect Action to the Closed state if the Quality Assignee has verified that the fix works. See Closing a Defect Action.
• Promote to Rejected. In the Evaluate, Open, or Test state, marks the Defect Action as Rejected (the action defined is not appropriate or required). See Rejecting a Defect Action. You cannot reject a Defect Action if it has been closed.

Use the Categories menu to view more information about the Defect Action. See Categories Menus.