Task vs. Ticket Logic: Classification & Responsible Team Assignment
What is the difference between Task and Ticket?
The Tasks Page includes two kinds of work items because operational work has different urgency levels. EVA separates planned operational work from urgent issue resolution to keep workflows clean and responsive. This separation prevents teams from mixing long-term work with immediate problem-solving in the same category.
In EVA:
- A Ticket is used for urgent issues, errors, or problems that require immediate attention and fast resolution.
- A Task is used for planned operational work that may not require urgent action, but still needs structured execution.
The Logic
The classification is controlled by the Task Type field. When a Task Type is selected:
- EVA automatically determines whether the item should be treated as a Task or a Ticket.
- EVA automatically assigns the appropriate Responsible Team based on the same Task Type value.
This means Task Type is not only a label. It directly controls routing and classification, ensuring the correct team receives the correct type of work item.
Why This Matters
Without automatic classification and routing, teams would have to manually decide how to categorize work, which creates delays and increases the chance of misrouting. By tying classification and Responsible Team assignment to Task Type, EVA standardizes intake and keeps execution predictable across different users.
Key Value Pillars
- Keeps urgent issue resolution separate from planned work
- Ensures Responsible Team assignment is consistent and automatic
- Reduces operational misrouting and confusion
- Supports faster resolution for urgent tickets