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

Switch to tickets endpoint with Cerb #1

Closed
abrenner opened this issue Jan 13, 2021 · 1 comment · Fixed by #3
Closed

Switch to tickets endpoint with Cerb #1

abrenner opened this issue Jan 13, 2021 · 1 comment · Fixed by #3
Assignees
Labels
enhancement New feature or request
Projects

Comments

@abrenner
Copy link
Contributor

Opening tickets currently uses the records endpoint which does not trigger bot behaviors with Cerb. By switching to the tickets endpoint bot behaviors should be triggered.

https://cerb.ai/docs/api/endpoints/tickets/

@abrenner abrenner added the enhancement New feature or request label Jan 13, 2021
@abrenner abrenner self-assigned this Jan 13, 2021
@abrenner abrenner added this to In progress in plugin-cerb Jan 13, 2021
@abrenner
Copy link
Contributor Author

Need to switch to parser endpoints as the tickets endpoint opens and replies to tickets as worker for Cerb and not as a client of Cerb.

https://cerb.ai/docs/api/endpoints/parser/

plugin-cerb automation moved this from In progress to Done Jan 15, 2021
abrenner added a commit that referenced this issue Jan 15, 2021
Enable Bot Behaviors on Ticket Creation and Replies Fixes #1

Switching to the parser endpoint rather then records will enable Cerb Bot Behaviors to work on ticket creation and replies. The records endpoint is a low level API that bypasses behaviors (for good reason). The records API is great for mass import of past ticket history where you would want behaviors to be triggered.

This should fix and close #1

Signed-off-by: Adam Brenner <adam@solidnetwork.org>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Development

Successfully merging a pull request may close this issue.

1 participant