Make timeline ticket updates aware of workflow actions
|Reported by:||Owned by:|
Ticket updates on the timeline are not currently workflow-aware. Instead of using workflow actions to distinguish between created, reopened, closed, and updated tickets, the timeline looks for status changes in the ticket_change table, and hard-codes certain verbs based on the ticket's status change.
These verbs overlap somewhat with the actions provided by the default workflow but in fact are completely independent of them: for example, if a ticket's status changes to "reopened", the timeline will render an event saying "Ticket .. reopened by .." regardless of what workflow action (if any) caused the ticket to arrive in the "reopened" state.
This overlap in responsibilities is confusing, and also means that certain assumptions about the ticket workflow are hardcoded into the timeline:
- The timeline assumes that a "reopened" state exists, and has some special meaning which should be distinguished from other ticket updates in the timeline
- The timeline does not know how to distinguish between any other types of ticket updates, even though some of these might be more special than others
It would be nice if the ticket updates in the timeline could be made workflow-aware, and if they could use historical workflow actions to render themselves instead of using status changes.