Case Types
Issues
Issue Icon 
Issues are similar to tasks . Typical differences between them are as follows:
- Issue efforts and progress are not tracked
- Issue s are not scheduled
- O nly one resource is assigned on each issue life cycle state
Issues can be used in relation to a project in place of sub tasks or can act as types of To Do List items .
Issues can easily be converted into tasks using custom actions or workflow rules to allow for resource time tracking and management.
Examples of issues may include informing a customer about a new document, preparing materials before a meeting or investigating the corporate competition.
There are no specific fields for the issue item type.
Requests
Request Icon 
A Clarizen request is a call for adjustment either internally or externally by your organization's customers. Request types may include (but are not limited to):
- Change request
- New task request
- Project request
- Customer request
Evaluating enhancements and change requests by the overall enhancement/request's effect on the project’s overall scope, budget, time,
and/or quality (typically performed by a ‘change management committee’) in the project management industry is common practice.
Once approved, the request may be converted into an actual project or task.
Bugs
Bug Icon 
A bug represents a software defect or malfunction. Bugs are usually used on software development projects and usually relate to a software component or to the project bug fixing phase.
This table represents bug item type specific fields:
|
Name |
Type |
Description |
|
Regression |
Boolean |
Whether bug is a regression from the previous versions. |
|
ImpactArea |
String(2000) |
Description of the resolution impact area |
|
FoundInBuild |
String(256) |
In which build was found |
|
IntegratedInBuild |
String(256) |
In which build integrated a fix |
|
ClosedInBuild |
String(256) |
In which build closed |
|
ReopenedInBuild |
String(256) |
In which build reopened back for fix due to fix failure |
Risks
Risk Icon 
The Project Management Body of Knowledge (PMBOK) define a risk as an uncertain event or condition that, if occurs, has a positive or a negative effect on a project’s objectives.
Risks should be identified, monitored and maintained throughout an entire project's life cycle.
Examples of risks may include a critical resource leaving during a project, possibility of an unanticipated requirement change, a project might have environmental effects, a project's funding may be behind schedule, etc.
Following table represents risk item type specific fields:
|
Name |
Type |
Description |
|
PercentProbability |
Double |
Probability of occurrence. |
|
Impact |
Integer |
Number from 1 to 5 representing the impact of the risk |
|
TriggerDate |
DateTime |
Trigger Date of the incident |
|
MitigationPlan |
String(2000) |
Description of the mitigation plan |
|
ContingencyPlan |
String(2000) |
Description of the contingency plan |
|
RiskRate |
Double |
Risk rating is measured by Impact * %Probability. Read only, Calculated. |
The above table does not match the risk form in Clarizen