getsentry
Cannot create issue with ClickUp integration
Environment
SaaS (https://sentry.io/)
Steps to Reproduce
- add the clickup integration
- try creating a clickup issue using the integration
- the external-issue-actions endpoint throws a 400 - bad request with the following response:
{"error":"Error communicating with Sentry App service"}
Expected Result
users should be able to create clickup issues using the integration
Actual Result
Product Area
Settings - Integrations
Link
No response
DSN
No response
Version
No response
┆Issue is synchronized with this Jira Improvement by Unito
![getsantry[bot] avatar](https://avatars.githubusercontent.com/in/66573?v=4 "Published by a pub.dev verified publisher"){kind=small}
@dalnoki is this issue reported by clickUp or a clickUp customer? Asking because clickUp is a 3rd party integration created by ClickUp and they're the ones providing support for it.
Looking at the dashboards on our side it looks mostly healthy.
Hello @sentaur-athena. I'm the original issue reporter. I'm a customer of sentry & clickup. I did start out by contacting clickup to get this fixed. They sent me over to sentry.
I'd appreciate if you could just connect between Sentry & Clickup to get this on it's way. ;-)
Best regards Martin
@SkyhopperZH thanks for the details. The way we support 3rd party integrations is that we provide support for the platform and ensure the platform is healthy while the integration provider provides support for the health of their integration. Checking the logs I don't see any platform issues, I also don't see this as persisting problem with clickup.
Here are some errors that I see some clickup users are facing.
404 Client Error: for url: https://api.clickup.com/sentry/webhook
SafeHTTPSConnectionPool(host='api.clickup.com', port=443): Read timed out. (read timeout=2.0)
Either can throw a bad request from external-issue-endpoint.
I can't look further without more details. @dalnoki is there a support ticket associated with this?
@sentaur-athena: I'd be happy to assist if you need me as the end user to run something. I'd require instructions though, as Sentrys UI is providing no guidance or context at all on why the call to create an issue is failing.
I sent Dominic from the clickup team a link to this issue. He was handling the ticket of the investigation from the clickup side. Maybe it helps.
Best regards Martin
@sentaur-athena can we have an update on this issue? The issue continues to affect the original reporter of the issue.
For your investigation: I could not reproduce the issue on my organisations (both on the same plan as the affected user, one in the US and one in the EU data region): Link1 Link2
Yes, will prioritize investigation. I couldn't repro too but seems like @dalnoki has an example from the Jira ticket attached.
Adding some information gathered since the last message (more details including PII are in the shadow ticket).
This seems to affect one specific user (the original reporter) and there are "500 Server Error: Internal Server Error for url: https://api.clickup.com/sentry/create" when communicating with ClickUp.
The tasks in ClickUp created using a second user have the name of the requester as the creator of the task.
Uhm folks, would you mind taking care of this issue? Its been 2 months already.
@SkyhopperZH hi! Rodolfo's comment above is the findings for the investigation. The main thing we found was we were only able to reproduce on only one user in the org. When that user tries to create a ticket and Sentry communicates that to Clickup, Sentry got back a "500 Server Error: Internal Server Error for url: https://api.clickup.com/sentry/create" from Clickup.
At this point we can't debug further as we don't know why Clickup is sending back 500s for only one user. I'd point you to Clickup to see if they can give more insight to the 500.
@Christinarlong Both parties keep pointing to the other side. I need you guys working together with clickup to fix your customers issue! After all it's you claiming that it's clickups problem. I can only see your system throwing a generic error.
@SkyhopperZH that's the nice thing about being open source. Please refer this ticket in your ClickUp communications and ask their engineers to follow-up about the error. They can also comment on the github issue and we would be happy to work with them. At this point it is clear to us that this is internal issue with their server though so I close the issue.