Name |
The auto-generated name. |
Type |
The issue type, used for classification. |
Problem Category |
Only shows if the Semiconductor IP Classify and Reuse is also used. Why the issue was submitted. Can be any of
these:
- How Do I?
- Enhancement Request
- Other
- Problem Report
|
Description |
Details about the issue. |
State |
The current state of the issue in its
lifecycle. Does not show for Issues
against DesignSync files or folders. |
Lifecycle |
Only shows if the Semiconductor IP Classify and Reuse is also used. The states the issue must pass through to be
resolved. The current state shows in a darker color. When
editing, click Promote or
Demote if needed. Otherwise, keep
No Change selected. You can only
promote or demote the issue one state at a time. Actual
promotion occurs when you click
Done. |
Last State Change |
Date when the issue was last promoted or
demoted. |
Owner |
The owner of the issue. In edit mode, you cannot
change the owner. Instead, use the Transfer
Ownership action. |
Originator |
The person who created the issue. |
Originated Date |
The date on which the issue was created. |
Subscribers |
Only shows for Issues against DesignSync files or
folders. List of users who have subscribed to be notified when the
issue is modified, promoted or demoted, or the discussion is
appended. An asterisk (*) indicates the user is subscribed to some,
but not all, events for the issue. When editing, click to add additional people to the list.
The edit page shows the usernames (not the first name, last
name) of people. |
Modified Date |
The date on which the issue was last modified. If
not modified, this date is the same as the Originated Date. |
Waiting On |
The person or department who must next respond to
the issue. Values are Unassigned, Analyst, Customer, or
Engineering. |
Escalation Required |
Indicates whether the issue requires upper
management support for resolution. |
Wait On Date |
The date that the person listed
in the Waiting On field should have responded by. (That is, by not
responding, the person has held up the Issue since the date
specified in this field.) The date can be set to any prior date, but
not earlier than the Issue's originated date. |
Estimated Start |
The estimated date on which the issue resolution
will begin. |
Estimated Finish |
The estimated date when the issue should be
resolved. |
Internal Priority |
The relative importance of the issue within the
host company. Values are Unassigned, P0, P1, P2, P3. |
Actual Start |
The actual start date. |
Actual Finish |
The actual date the issue was resolved. |
Priority |
The
relative importance of the issue, set when the issue was created or
modified. Values are Low, Medium, High, Pre-assigned. |
Resolution Date |
Date when the issue was
resolved. |
Resolution
Recommendation |
A recommendation for how to resolve the
issue. |
Action Taken |
A description of any action taken to resolve the
issue. |
Resolution
Statement |
A description of the actual resolution. |
Steps to Reproduce |
The procedure for reproducing the problem causing
the issue. |
Category |
Determines
the issue classifications for this issue. |
Classification |
Determines the Issue Manager responsible. Based
on Category and Classification, issue managers can be assigned and
notified automatically. |
Reporting
Organization |
The company associated with the issue. |
Policy |
The policy that governs the issue's
lifecycle. |
Co-owners |
People who are responsible for the issue. In
edit mode, if you select a new co-owner person or list, the new
co-owners replace the current
co-owners. The co-owner has full access to
the Issue regardless of the collaborative space and organization
that owns the Issue. The owner of the
issue cannot be assigned as a co-owner. If you select a
classification, the owner of this issue is defined by the
classification and that person cannot be assigned as a
co-owner. |
Problem Type |
Values are 3rd party, Defect, Not Determined, Ease
of Use, Functionality, Licensing, Installation, Mistake,
Performance, Platform, Training. |
Responsible
Organization |
The organization responsible for resolving the
issue. Editable only by Analyst or Issue Manager. You can only
change the Responsible Organization when the issue has been
promoted beyond the Create state. |
Discussions |
Only shows for Issues against DesignSync files or
folders. Any discussion threads created regarding
this issue. Click Attachments to view any
files attached to the discussion. When editing, enter any required
text in the box and click the Public Reply or Private Reply
button. You can also participate in discussions from your
Discussions page or the Discussions page for the issue. Only
employees of the host company, and its business units,
divisions, and departments, can view Private
messages. |