The job of this console
Log the issue, assign actions, close or promote to the service desk. Keep RAID honest.
Projects · Governance
Issues & Actions
Realized project problems and actions — not tickets unless you promote them, not risks that have not happened.
Scroll to Flowcharts. Scenario: Raise an issue and an action.
Already happened
Issues and actions on the project
Issues capture problems that occurred. Actions close them. Tickets are a different entity when SLA service is needed.
Projects → Issues & actions
Route
/project/issues
Org flag issuesEnabled
Manager · Project Manager · Executive · Admin
Seat at the table
PMs and executives. Assignees complete actions. Service agents work tickets.
The working rhythm
Log, assign, chase due actions, close. Steering pack reads governance.
Moments that bring you here
Blocked environment. Failed deploy. Customer complaint that is still a project issue. After a risk crystallizes.
ⓘ
Issue ≠ ticket ≠ risk
Pick the entity that owns the work. Do not triple-enter the same story.
Flowcharts
1 — Issue then action
Log what happened, assign an action, close or ticket.
flowchart TD
A[Open Issues] --> B[Log issue]
B --> C[Add action]
C --> D{Service desk?}
D -->|Yes| E[Create ticket]
D -->|No| F[Close on project]
- 1OpenProjects → Issues & actions.
- 2LogWhat already happened.
- 3ActionOwner + due.
- 4Close or ticketSLA lives on tickets.
Overview
Issues are realized. Risks are uncertain. Tickets are service-desk entities with SLA.
How to use
1. Actions need owners
Employee, not ‘TBD’ as the only owner.
2. Don’t dual-source
Pick issue or ticket as the working record.
3. RCA later
Use RCA when the product path says so.