Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement Ticket Management Page for Admins with Ticket Detail View, Search & Filters, and Status Update #965

Closed
IkkiOcean opened this issue Nov 9, 2024 · 2 comments · Fixed by #973
Assignees

Comments

@IkkiOcean
Copy link
Contributor

This issue focuses on creating the admin-facing interface where admins can manage support tickets, view detailed ticket information, search and filter tickets, and update ticket statuses. The goal is to provide an efficient way for admins to handle and resolve users' issues by offering essential tools for ticket management.

Description:

The admin interface will consist of the following components:

  1. Ticket List View:

    • A page where admins can see all the support tickets, with an overview of each ticket's basic details such as Ticket ID, Subject, Status, Assigned Agent, and Creation Date.
    • This list should be paginated to handle a large number of tickets effectively, and include sorting and filtering options to make ticket management more efficient.
  2. Ticket Detail View:

    • When an admin clicks on a ticket, they should be directed to a Ticket Detail View that shows detailed information about the ticket, including the ticket description, issue history, priority, and attachments (if any).
    • It should also display communication logs between the user and support agents, if applicable, and allow the admin to update the ticket’s status or assign/reassign the ticket to another support agent.
  3. Ticket Search and Filters:

    • A search bar for admins to search tickets by Ticket ID, Subject, or User.
    • Filters should be implemented to narrow down the tickets by criteria such as Status (Open, In-Progress, Resolved), Priority (High, Medium, Low), and Assigned Agent (if the ticket has already been assigned).
  4. Ticket Status Update:

    • Admins should be able to update the status of a ticket, such as changing it from Open to In-Progress, or Resolved.
    • This will help keep track of each ticket’s current progress and ensure that users are notified when their issue has been addressed.
  5. Assign/Reassign Ticket:

    • Admins should be able to assign tickets to specific agents or teams. If necessary, they should also be able to reassign tickets to other agents, depending on the workload and skillset required for handling specific issues.

Expected Outcome:

  1. Ticket List Page:

    • Admins will have an overview of all tickets, and be able to search, sort, and filter tickets by various criteria (ID, subject, status, priority, agent).
    • Pagination will ensure that even with a large number of tickets, admins can easily navigate through them.
  2. Ticket Detail View:

    • Admins will be able to see detailed information about a ticket, including its history, communication logs, status, priority, and any attachments.
    • The ability to update the ticket status and assign/reassign agents will help admins manage the tickets more effectively.
  3. Search and Filter:

    • Admins will be able to quickly find tickets that require their attention, either by searching for specific tickets or by using filters to narrow down the results.
  4. Ticket Status Update:

    • Admins will be able to keep track of each ticket’s progress and update its status as work is done on it, ensuring a seamless workflow for ticket resolution.
  5. Assign/Reassign Agent:

    • Admins can assign or reassign tickets to agents, ensuring that each ticket is managed by the appropriate team member.
Copy link
Contributor

github-actions bot commented Nov 9, 2024

Thank you for creating this issue! 🎉 We'll look into it as soon as possible. In the meantime, please make sure to provide all the necessary details and context. If you have any questions or additional information, feel free to add them here. Your contributions are highly appreciated! 😊

You can also check our CONTRIBUTING.md for guidelines on contributing to this project.

Copy link
Contributor

Hello @IkkiOcean! Your issue #965 has been closed. Thank you for your contribution!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants