Project Issue iCube enables you to create ad-hoc reports that help you analyze issues in your projects in terms of status, priority, type, due date, and proposed solution among other perspectives. This iCube provides a list of attributes and metrics using which you can create new dossiers.
| Attributes | Description |
|---|---|
| Issue | Name of the issue |
| Issue Assigned To | Person primarily responsible for working on the project issue |
| Issue Business Function | Business function to which the issue is tied |
| Issue Created By | Person who created the project issue |
| Issue Creation Date | Date and time on which the issue was created |
| Issue Description | Short description of the issue |
| Issue Detailed Description | Detailed description of the issue |
| Issue Due Date | Date by when the issue is expected to be resolved |
| Issue Escalation level | The level of escalation of the issue. It indicates if the issue impacts a project or a program. |
| Issue Identification Date | Date when the issue was identified |
| Issue Priority | Priority of the issue. Possible values: Planning, Low, Medium, Normal, Intermediate, High, and Critical. |
| Issue Proposed Solution | Solution proposed to resolve the issue |
| Issue Status | Status of the issue. Possible values: New, Open, Pending Closure, Closed, and Cancelled. |
| Issue Type | Type of the issue. Possible values: Business Function, Staffing, Project, Testing, Technical, and General. |
| Project | Collection of tasks that have to be completed to achieve a particular goal |
| Project Number | Unique identifier to identify a project |
| Metric Name | Description | Formula | Expected Value |
|---|---|---|---|
| No. of Issues | Count of issues | Count([No. of Issues]) | 0 or >0 |
© 2022 Digital.ai Inc. All rights reserved.