-
-
Notifications
You must be signed in to change notification settings - Fork 4.3k
Sentry does not show Integration Errors- such as title length exceeded in Jira ticket creation #55524
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
Comments
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. |
Related to : https://sentry.zendesk.com/agent/tickets/144883 |
Related to: https://sentry.zendesk.com/agent/tickets/145118 |
Same issue was reported by a user on this ticket: https://sentry.zendesk.com/agent/tickets/145221 |
@Dhrumil-Sentry one additional comment on this issue: when you run into the error the "Create issue" button is disabled and stays that way after changing the title/summary. User needs to restart the process for the button to be enabled again. |
Yes exactly the fact that the button stays grayed out when you adjust the subject is really not helpful Jira also gives us the exact same message when we try to create a ticket over 255 characters so i wonder if its something JIRA changed or the plugin changed that weve never seen his issue before Can the option be made to auto substring the summary somewhere? |
We have a project planned to communicate these errors to users. Though it's not prioritized for this quarter. I'll post an update on timelines when we have one. |
since we know the max field could we truncate the data before calling Jira? Not sure it makes sense to try truncating things in sdks or at ingestion time due to 3rd integration party constraints |
@GabeVillalobos does #85756 fix this issue? if so, can we close it? |
Hey, I have customer who is running into this problem for the jira server integration. Would it be possible to support automatically truncating issue titles over 255 for it too, as we did for jira? https://sentry.zendesk.com/agent/tickets/151704 |
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
The text was updated successfully, but these errors were encountered: