Assigned
Status Update
No update yet.
Comments
jp...@google.com
Generated Metadata
- Summary: The Google Chat webhook integration with Gitlab is not creating new threads as expected. The developer has tried using the
MESSAGE_REPLY_OPTION_UNSPECIFIEDandREPLY_MESSAGE_FALLBACK_TO_NEW_THREADparameters, but neither is working. - Tags:
Additional resources:
https://developers.google.com/workspace/chat/quickstart/webhooks https://stackoverflow.com/.../how-to-make-my-slackbot-reply-in-a-thread-i... https://github.com/googleworkspace/google-chat.../webhook/thread-reply.g... https://stackoverflow.com/.../having-trouble-posting-a-child-reply-message-... https://developers.google.com/workspace/chat/api/reference/rest/v1/cards
You can
bl...@google.com
Automated by Blunderbuss job workspace-devrel-public-issue-tracker-blunderbuss-autoassigner for config shared_rate_limited_assign for component 350158.
Description
Before opening a new issue, please
+1to vote.Description
When using the Gitlab integrations with Google Chat to send out a notification to a Google Chat space/room using webhooks it always sends the notification to the same thread instead of starting a new thread, this makes it very hard for colleagues to see what are the new updates on a gitlab repo.
Tried followinghttps://developers.google.com/workspace/chat/api/reference/rest/v1/spaces.messages/create#query-parameters and tried both MESSAGE_REPLY_OPTION_UNSPECIFIED and REPLY_MESSAGE_FALLBACK_TO_NEW_THREAD but none of them worked. The former says that it should start a new thread regardless if threadKey is set or not, but that isn't the case for some reason.
Are there any other workarounds?
Impact
No business impact, it's just difficult to see new updates from gitlab as you need to click on the thread icon and click on the old thread where all gitlab notifications are, instead of just seeing the new message at the bottom of the chat space