You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A ticket can currently be assigned to an analyst, which works well for many scenarios. However, in larger organizations, responsibilities around a ticket are often more complex.
There is often a distinction between:
The person ultimately responsible for the ticket
The people actively working on the ticket
Additional stakeholders who should be kept informed
Suggested improvement
Introduce separate ticket roles similar to those found in many enterprise ITSM solutions:
Owner (Primary Responsible Person)
The Owner is ultimately responsible for the ticket and ensures that it progresses and is resolved.
Characteristics:
Single user assignment
Overall accountability
Visible in ticket overviews and reports
Remains responsible even if multiple people work on the ticket
Assignees (Working Analysts)
Assignees are the users actively working on the ticket.
Characteristics:
One or multiple users
Optional support for teams
Receive notifications and assignments
Can update and work on the ticket simultaneously
Examples:
Infrastructure specialist
Network administrator
Application administrator
Watchers (Interested Parties)
Watchers are informed about ticket activity but are not responsible for processing the ticket.
Characteristics:
One or multiple users
Optional support for teams
Receive updates and notifications
Read-only involvement
Typical examples:
Managers
Team leaders
Key users
Project managers
External stakeholders
Example
Ticket: VPN Connection Problems
Owner: Max
Assignees: Network Team, Maria
Watchers: Paul, Key User Group
This makes it immediately clear:
Who is responsible
Who is working on the issue
Who should stay informed
Benefits
Clearer ownership and accountability
Better collaboration across multiple analysts
Reduced confusion around responsibilities
Improved communication with stakeholders
Better support for larger teams and enterprise environments
More flexibility than a single analyst assignment
Improved reporting and escalation handling
Many tickets involve several specialists, supervisors, and stakeholders. Separating responsibilities into Owner, Assignees, and Watchers would provide a much more realistic representation of how ticket processing works in many organizations and would make FreeITSM even more suitable for larger teams.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Current situation
A ticket can currently be assigned to an analyst, which works well for many scenarios. However, in larger organizations, responsibilities around a ticket are often more complex.
There is often a distinction between:
Suggested improvement
Introduce separate ticket roles similar to those found in many enterprise ITSM solutions:
Owner (Primary Responsible Person)
The Owner is ultimately responsible for the ticket and ensures that it progresses and is resolved.
Characteristics:
Assignees (Working Analysts)
Assignees are the users actively working on the ticket.
Characteristics:
Examples:
Watchers (Interested Parties)
Watchers are informed about ticket activity but are not responsible for processing the ticket.
Characteristics:
Typical examples:
Example
Ticket: VPN Connection Problems
This makes it immediately clear:
Benefits
Many tickets involve several specialists, supervisors, and stakeholders. Separating responsibilities into Owner, Assignees, and Watchers would provide a much more realistic representation of how ticket processing works in many organizations and would make FreeITSM even more suitable for larger teams.
All reactions