Proposal: Web Panel Ticket System for Chat (with Existing Authentication)

[bberka]

Description

Investigate and potentially implement a web panel ticket system that allows users and admins to continue ticket chats through a web link, leveraging the existing web panel authentication. While the primary goal of the application is to provide a ticket system for Discord, adding web UI-based chat would offer additional flexibility and accessibility.

---

Why This Feature is a Proposal

• Core Functionality: The primary goal of the application is to provide a ticket system for Discord, and web UI-based chat is not currently a core requirement.
• Resource Intensive: Implementing a full web-based chat system would require significant development effort.
• Evaluation Needed: It's important to assess the potential benefits and drawbacks of adding this feature before committing resources to its implementation.

---

Proposed Implementation Details

1. Web UI Chat Interface:

   • Create a chat interface in the web panel to display ticket messages and attachments.
   • Allow users and admins to send and receive messages through the web UI.

2. Discord Integration:

   • Ensure that messages sent through the web UI are synced with the corresponding Discord ticket channel.
   • Any messages sent in the Discord ticket channel should also be displayed in the web UI.

3. Authentication:

   • Use existing web panel authentication to verify user identity.
   • Ensure the user has the appropriate permissions to access the ticket.

4. Message Handling:

   • Implement logic to handle formatting, attachments, and other message properties.
   • Ensure that messages are displayed correctly in both the web UI and Discord.

5. Real-Time Updates:

   • Use SignalR or similar technologies to provide real-time updates for new messages.

---

Assessment Questions

• Is there a demand from users or admins for a web panel ticket system with chat?
• What are the potential benefits of adding this feature (e.g., improved accessibility, support for users without Discord)?
• How much additional complexity would this feature add to the codebase and UI?
• Are there alternative solutions (e.g., linking to Discord) that could provide similar benefits with less effort?

---

Acceptance Criteria

Before implementation, the following questions should be answered:

• Use cases for a web panel ticket system with chat are identified.
• Potential benefits and drawbacks of adding the feature are evaluated and documented.
• Impact on code complexity is assessed.
• If the benefits outweigh the costs, the following acceptance criteria apply:
  • Users and admins can access ticket chats through a web link.
  • Existing web panel authentication is used to verify user identity.
  • Messages sent through the web UI are synced with the corresponding Discord ticket channel.
  • Real-time updates are implemented for new messages.

---

Priority

Low (Proposal)

---

Additional Notes

• This feature is marked as a Proposal because it requires further evaluation to determine its necessity and feasibility.
• Gather feedback from users and admins to assess the potential benefits and drawbacks before committing to implementation.