Open rodolfoBee opened 1 year ago
Assigning to @getsentry/support for routing ⏲️
Routing to @getsentry/product-owners-settings-integrations for triage ⏲️
This is a larger issue at Sentry wherein today we don't tell users why an action via integration fails- which is likely due to our interactions with 3rd party APIs.
This is a very valid ask and I am adding this to our backlog
I believe this may also be preventing Jira tickets from being created by alerts when the title length is exceeded. I have several issues that should have created linked tickets but have not, and there is no other indication as to why.
Environment
SaaS (https://sentry.io/)
Steps to Reproduce
The ticket creation will silently fail. In the network tab you will be able to see the failed request and the response:
The summary length cannot be changed in Jira, and the issue title in Sentry can easily be longer than 255 when using the event's message as title.
Expected Result
Issue is not created but the UI shows the error in some way.
Actual Result
No warning/error message in the UI.
Product Area
Settings - Integrations
Link
No response
DSN
No response
Version
No response