Setting Up User Codes
To set up user codes, use the Defect Relationship Types (RQ_RELATION_TYPE), Defect Causes (RQ_UD_DEF_SUSPEC), Defect Symptoms (RQ_UD_DEF_SYMPTM), Defect Status State (RQ_UD_ST_REASON), Defect Status State Reason (RQ_UD_ST_ST_RSN), Defect Status (RQ_UD_ST_STATUS), and Status Combinations (RQ_UD_STAT_COMBO) components.
This topic discusses how to set up user codes.
Page Name |
Definition Name |
Usage |
---|---|---|
RQ_UD_DEF_SYMPTM |
Define defect symptom codes to provide consistent problem symptom descriptions and to facilitate data entry. |
|
RQ_UD_DEF_SUSPEC |
Define defect cause codes to provide consistent potential problem cause descriptions and to facilitate data entry. |
|
RQ_UD_ST_STATUS |
Define defect status codes. |
|
RQ_UD_ST_REASON |
Define status states to describe defect status more specifically. |
|
RQ_UD_ST_ST_RSN |
Define status-state reason codes to explain why a defect is in a particular status state. |
|
RQ_UD_STAT_COMBO |
Define status-state combinations to control permissible transitions. |
|
RQ_RELATION_TYPE |
Define defect relationship types to describe dependencies and relationships among defects. |
Use the Defect Symptoms page (RQ_UD_DEF_SYMPTM) to define defect symptom codes to provide consistent problem symptom descriptions and to facilitate data entry.
Navigation
Image: Defect Symptoms page
This example illustrates the fields and controls on the Defect Symptoms page.
![Defect Symptoms page](img/i-42c12a96n-757d.png)
Note: The system provides sample field values. You can configure these codes to match product offerings or meet business objectives.
Defect symptom codes describe common symptoms that your customers might experience. For example, when a faulty motherboard causes a computer to crash, the symptom is the crash.
Field or Control |
Definition |
---|---|
Symptom and Description |
Enter a unique code and description that represent the defect symptom. |
Use the Defect Causes page (RQ_UD_DEF_SUSPEC) to define defect cause codes to provide consistent potential problem cause descriptions and to facilitate data entry.
Navigation
Image: Defect Causes page
This example illustrates the fields and controls on the Defect Causes page.
![Defect Causes page](img/i-42c12a96n-74f7.png)
Defect cause codes describe the actual cause of a problem. For example, when a loud squealing noise comes from the bottom of a refrigerator, the actual cause is a bad compressor bearing.
Field or Control |
Definition |
---|---|
Suspected Cause and Description |
Enter a unique code and description that represent the suspected cause of the defect. |
Use the Defect Status page (RQ_UD_ST_STATUS) to define defect status codes.
Navigation
Image: Defect Status page
This example illustrates the fields and controls on the Defect Status page.
![Defect Status page](img/i-42c12a96n-75ca.png)
Defect status codes describe the defect's most fundamental status in the problem resolution (fix) cycle. The values OPEN and CLOS (closed) are delivered with the system. Add additional values as required; however, the delivered values should be adequate for most needs.
Field or Control |
Definition |
---|---|
Status Code and Description |
Enter a unique four-character code and description that represent the defect status. |
Use the Defect Status State page (RQ_UD_ST_REASON) to define status states to describe defect status more specifically.
Navigation
Image: Defect Status State page
This example illustrates the fields and controls on the Defect Status State page.
![Defect Status State page](img/i-42c12a96n-7556.png)
Status states define the defect's status in the resolution process more specifically than status codes. For example, when you close an enhancement request, you may do so because you have completed the process or because you decided not to enhance the product as requested. Each status state is linked to a valid status and is available on the Defect page when the corresponding status is chosen.
Field or Control |
Definition |
---|---|
Status Code |
Select the description of the defect's status in the resolution process. Delivered status options are: Closed and Open.Define status codes on the Defect Status page. |
State and Description |
Enter a unique code of up to four characters and a description to represent the status state. |
Use the Defect Status State Reason page (RQ_UD_ST_ST_RSN) to define status-state reason codes to explain why a defect is in a particular status state.
Navigation
Image: Defect Status State Reason page
This example illustrates the fields and controls on the Defect Status State Reason page.
![Defect Status State Reason page](img/i-42c12a96n-7597.png)
Use the Reason field to describe why a defect resolution has a particular status and state. One status-state combination might have several reasons. For example, a defect may be set with a status state of Closed - Do Not Fix because the product is no longer supported or because you have determined that the defect complaint should really be an enhancement request. Each status-state reason is linked to a status and state combination and is available on the Defect page when a user chooses the corresponding status and state.
Field or Control |
Definition |
---|---|
Status |
Select the description of the defect's status in the resolution process. Delivered status options are: Closed and Open. Define status codes on the Defect Status page. |
State |
Select the state that you want to associate with the defect status. States define the defect's status in the resolution process more specifically than status codes. Select either Deferred, Do Not Fix, Fixed, or Withdrawn. |
Reason and Description |
Enter a code of up to three characters and a description to further explain the reason for the status-state combination. |
Use the Status Combinations page (RQ_UD_STAT_COMBO) to define status-state combinations to control permissible transitions.
Navigation
Image: Status Combinations page
This example illustrates the fields and controls on the Status Combinations page.
![Status Combinations page](img/i-42c12a96n-75ed.png)
As a defect or enhancement request moves thorough the resolution process, you want to change the status-state combination to reflect its progress. However, certain changes do not make sense. For example, if an enhancement request's status is Open - Deferred, you should not change it to Closed - Fixed without passing through the verify, fix, and test stages.
Use this page to control which transitions are permissible. Define combinations for all possible transitions, including reverse transitions. For example, if a software fix fails in testing, it must be returned to the developer. In this case, you need a valid status combination that allows the change to go from Open - Fixed back to Open - To Test in development.
Field or Control |
Definition |
---|---|
Status Code From |
Select the description of the beginning status code from the codes that you defined on the Defect Status page. |
State Code From |
Select the description of the beginning state code from the codes that you defined on the Defect Status State page. |
Status Code To |
Select the description of the new (after the combination change) status code from the codes that you defined on the Defect Status page. |
State Code To |
Select the description of the new state code after the change from the codes that you defined on the Defect Status State page. |
Use the Defect Relationship Types page (RQ_RELATION_TYPE) to define defect relationship types to describe dependencies and relationships among defects.
Navigation
Image: Defect Relationship Types page
This example illustrates the fields and controls on the Defect Relationship Types page.
![Defect Relationship Types page](img/i-42c12a96n-74e9.png)
Sometimes, two or more defect cases are related to one another, or the solution to a defect may be dependent on the solution to a previous defect. Defect relationship types describe these dependencies. All defect relationships fall into the general categories of hierarchical or equivalent.
An equivalent relationship is two or more defects having the same cause. One fix resolves multiple cases. A hierarchical relationship is an instance when one case cannot be resolved without first resolving another.
Field or Control |
Definition |
---|---|
Relationship Type |
Enter a unique code up to five characters to represent the relationship type. |
Parent Label and Child Label |
If you are defining a hierarchical relationship, enter a label value for both the parent and the child defects. These labels are used on the Related Defects page to describe the relationship. |
Equivalent Label |
If you are defining an equivalent relationship, enter a label value to appear on all related cases. |
Hierarchical |
Clear this check box to define an equivalent relationship type. |