Issue Lifecycle

You can list issues. However, only a Leader or Issue Manager can change the owner or the type for an issue.

Some actions on issues occur automatically based on the lifecycle state and some must be done by a specific user before the issue can move to the next state.

This page discusses:

Draft

You can create an issue. Upon creating an issue, depending on the Category and Classification, the Issue Owner is changed to the Author or Issue Manager, associated with that Classification. The Issue Manager begins the analysis of the Issue and enters the Estimated Dates, then promotes to the To Do state.

To Do

This state assigns a person to the issue. Optionally, the owner of the issue can complete the issue early if resolved. A resolution can be as simple as a phone call to the customer or a user error. A person is notified as soon as they are assigned to an issue. A notification is sent to the originator that the issue is being addressed. When using Issues in Collaboration and Approvals, the Estimated Start and Finish Date cannot be changed beyond this point. When using Issue Management, you can continue to change the Estimated Start and Finish Date as they change.

In Work

Upon promotion to this state, the Actual Start Date is populated with the system date. The issue is now started and Assignee can work on the issue.

In Approval

Issue is forwarded for approval, using the routing for approval process.

Completed

Upon promotion to this state, the Actual End Date populates with the system date. The Issue is now considered resolved.