When discussing “Issue Responsibilities,” your first thought might be the issue’s assignee, or possibly the submitter of the issue. However, there are a number of different roles within Issuetrak that tie into issue resolution and can indicate responsibility.
Have a look at the list below of roles that users and agents can hold on a particular issue:
|Submitter||The person with the problem that the issue is for.|
|Enterer||The person logging the issue.|
|Assignee||The owner of the issue.|
|Next Action||An Agent or Group that takes temporary control of an issue.|
|Task Assignee||The owner of part of the issue process/workflow.|
|Administrator||An Agent or End User with administrator permissions.|
Each of these roles carries responsibility in resolving that issue -- whether it’s a single step that needs to be taken or a much larger role in the process. In addition, in order to close or edit the issue, you must have a role in the issue, even if you possess the proper permissions to see it.
The Submitter is the person who is experiencing the problem. Though they may not have an active role in working the issue, they will still be updated throughout the resolution process. They also have a responsibility to respond to the requests of staff that are assigned their issue -- failure to respond may result in delaying the resolution of the issue until the right information can be collected.
The Enterer is the person who logged the issue into Issuetrak.
This is the Agent or Group that “owns” the issue. The issue may be assigned to a person or a group manually by the Enterer, or it may be auto-assigned using Issuetrak’s automation features. The Assignee typically has responsibility for completing the bulk of the work within their assigned issue.
An Agent or Group that has been assigned “Next Action” takes temporary control of an issue -- essentially, they have been assigned the issue’s responsibility without actually having been assigned the issue itself. Next Action is a useful tool for providing temporary visibility into issues that a particular Agent typically might not see. For example, suppose an employee’s assistance is needed on an otherwise invisible HR ticket. In that case, Next Action can be used to provide visibility into that ticket for that particular employee for as long as Next Action is active.
Another scenario where this feature can be helpful is when the issue is assigned to a group, but then assigned Next Action to a specific team member. The group would then have visibility and responsibility to resolve the issue, while the individual team member is designated to actually work on the issue. This allows team members to pick up for a Next Action user if they are out of work for any reason, or to quickly reference the issue information if someone calls to check on its status.
Next Action can be beneficial in cases where a team doesn’t want issue ownership to ever change, but assistance from other departments may be required.
Issuetrak supports Tasks through its Task Manager, which allows you to build out simple or complex branching workflows within an Issue. Tasks can be assigned out so that, if a particular User, Agent, or Group needs to complete a step within a larger issue, they can be assigned that step specifically and receive notifications reminding them to take action.
Want to know more about Issuetrak’s Task Manager? Have a look at our main article on this subject to walk you through it!
Administrators have their own roles and responsibilities within issues. They can manage the process and help ensure that an issue is resolved, closed, and that the resolution and service meets organizational standards. Administrators have unrestricted access to the site and can view any issue.
Only users with one of the following permissions are labelled as administrators:
- Sys Admin
- Can access and maintain Administration functions
- Allowed Read Only access to Administration information
If you have any questions or would like the assistance of our product experts, please do not hesitate to contact us with any questions.