-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Integration with ClickUp doesn't work #55006
Comments
Assigning to @getsentry/support for routing ⏲️ |
Routing to @getsentry/product-owners-settings-integrations for triage ⏲️ |
@alvar-hoenig Seems like an issue with ClickUp's service. You'll need to contact their support. |
Hi,
I finally got the response from ClickUp. They say the problem is on your
side. Please I attached a screenshot of the error which ClickUp is getting
from Sentry.
Thanks.
Best Regards,
*Alvar Honig*
Director of Engineering | Momence <https://momence.com>
…On Mon, Aug 21, 2023 at 2:14 PM Stephen Cefali ***@***.***> wrote:
@alvar-hoenig <https://github.com/alvar-hoenig> Seems like an issue with
ClickUp's service. You'll need to contact their support.
—
Reply to this email directly, view it on GitHub
<#55006 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BAF23ZW3NIDSQDOQ5DZDYALXWOQQXANCNFSM6AAAAAA3UWU2OM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@alvar-hoenig You didn't attach a screenshot. Also, the error you showed shows that Sentry got a non 2xx response code from ClickUp. Which means they are returning an error. Please include the screenshot of ClickUp's response. |
Hi, The error says "Error: There is no free venue available for selected time." Your comment about non 2xx response code doesn't make sense to me. The error I am attaching is error which CU got when called Sentry. Not the other way around. That's what CU told me. Anyway, you understand that I, as a customer, don't enjoy the position of being a middleman between Sentry and CU. It would be great if you talk directly to CU, if you have any additional questions. That's what I would expect from two service which claim they have been integrated. Thanks. Best regards, |
@alvar-hoenig You are a bit confused the error you are showing is the error for the Sentry issue you are trying to make a ClickUp issue for. That's why it's in the payload section. That error came from your application, not Sentry. The error you're looking for would be in the response, not the payload.
In fact, as I mentioned before, the error you are showing is actually from your application, not Sentry or ClickUp.
I understand the frustration of being caught in the middle, but I don't actually work at Sentry full-time anymore so I can't talk to them on behalf of Sentry. Tagging @Dhrumil-Sentry to see if he can help. |
Got it, thanks. The screenshot is from the ClickUp support. In other words, they sent me a useless screenshot to share with the Sentry team. Nice. |
@alvar-hoenig Can you send this public GH thread to the ClickUp folks? We can debug it with them here. |
Thanks, Danny. In fact I did. They only complained I shouldn't solve Sentry problems with Stephen who doesn't work in Sentry any more. |
Sentry is contracting work out to @scefali. He's no longer working at Sentry, but he's working with Sentry. I'm here to figure out priorities for the team + contractors. I'll let the ClickUp folks chime in here because I need more info. |
Closing, since issue is stale. Feel free to open a new one, if this problem is still happening. |
Environment
SaaS (https://sentry.io/)
Steps to Reproduce
I set up the integration between sentry and clickup. When I try to create a clickup task from sentry, it works for me, however not for anyone else. They will get an error - see screenshots. Any idea what can be wrong about our set up? Creating tasks directly from sentry errors is crucial for us to using this integration.
Thanks.
Expected Result
Every CU member should be able to create CU task from sentry.
Actual Result
Getting error
Product Area
Other
Link
No response
DSN
No response
Version
No response
The text was updated successfully, but these errors were encountered: