[Enhancement]: Actual Tickets Integration #47
Assignees
Labels
Status: Planned
Something that will try to be done in the future.
Type: Enhancement
An improvement to an already existing feature.
Milestone
Comments
Tech-TTGames
added
Type: Enhancement
|
But I'm probably gonna have a stroke writing an API to add to all of this |
|
GL with this when you get to it, i'm sure its going to be one hell of an update |
Tech-TTGames
added a commit
that referenced
this issue
May 7, 2023
## Description Do get the user and actually only bot-channels. More efficient. ## Changes Made - Integration endpoint implemented - API created ## Issues Resolved - Closes #47 - Closes #40 ## Checklist - [x] My code follows the style guidelines of this project. - [x] I have reviewed my own code and ensured it passes all linting tests. - [x] I have commented my code, particularly in hard-to-understand areas. - [x] I have made corresponding changes to the documentation. - [x] My changes generate no new warnings.
github-project-automation
bot
moved this from 👀 In review
to ✅ Done
in Tickets-Plus Plans and Backlog
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
The feature of future! We will actually get data from the main Tickets. Bot involves another whole batch of annoyances and so is planned for v0.1.1.
Description
Basically we will have to make an API for the Tickets bot to send POST requests to.
We would then get this great package:
{
"guild_id": "508392876359680000",
"user_id": "585576154958921739",
"ticket_id": 123,
"ticket_channel_id": "508410703439462400"
}
The Basis
This would remove the need for ticket users and change the mechanism based on which we run our opening actions. Making the code more reliable for the intents and purposes.
Use Case
We can get user_id reliably. As it currently stands we have no practical way for doing so.
Impact
A lot of work. Reliability. Less setup? They would have to add the integration on panel.ticketsbot.net
Alternatives
The one is currently in use yes.
Screenshots
No response
Additional Information
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: