This repository was archived by the owner on Sep 3, 2025. It is now read-only.
Adds triage button #3632
Merged
Adds triage button #3632
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds a triage button that is only shown then the case is in the "New" state. Click it simple moves the case to "triage" state.
Additionally, this PR adds support for processing case messages (this wasn't working before apparently) by modifying the way we look up conversation context to allow for specifying thread_id together with conversation_id.
With these case messages now being properly processed, a message listener moves the case to triage on the first non-bot message.
Dispatch won't currently allow for participant conversation and the case to stay in the "New state". I'm not sure if there is a use case for such a scenario.