RIDAC Issue form
Use the RIDAC Issue form to create and manage issues that affect your demand or project planning items. Track planning challenges, obstacles, and problems that need resolution.
| Field | Description |
|---|---|
| Number | Unique identifier for the issue. This field is auto-generated when the issue is created. |
| State | Current status of the issue. The available options are Pending, Open, Work in Progress, Closed Complete, Closed Incomplete, and Closed Skipped. |
| Short description | Brief, concise summary of the issue. This field is required and appears as the title of the issue record. |
| Description | Detailed information about the issue, including context, background, and any additional relevant details. |
| Priority | Priority level of the issue. The available options are 1 - Critical, 2 - High, 3 - Moderate, 4 - Low, and 5 - Planning). This helps with issue prioritization and resource allocation. |
| Estimated Cost | Estimated cost in currency (for example, USD) to resolve the issue. Helps with financial tracking and planning. |
| Impact | Impact level if the issue is not resolved. The available options are 1 - High, 2 - Medium, 3 - Low). This indicates the severity of the issue on planning objectives. |
| Due date | Target date by which the issue should be resolved. |
| Assigned to | User or team responsible for resolving the issue. |
| Planning Item | The planning item (project or demand) that this issue is associated with. This field is auto-populated when an issue is created from a planning item context. |
| Parent | Parent issue, if this issue is a child of another issue. Used for issue hierarchy and rollup tracking. |
| Work notes | Internal notes and updates about the progress of issue resolution. Used to track work history and communication. |