Skip to content

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

Closed
rodolfoBee opened this issue Aug 31, 2023 · 13 comments · Fixed by #91057

Comments

@rodolfoBee
Copy link
Member

Environment

SaaS (https://sentry.io/)

Steps to Reproduce

  1. Add jira integration to a organisation
  2. Try to create a Jira issue from Sentry
  3. In the title field, add a message longer than 255 characters

The ticket creation will silently fail. In the network tab you will be able to see the failed request and the response:

{"summary":["Summary can't exceed 255 characters."]}

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

@getsantry
Copy link
Contributor

getsantry bot commented Aug 31, 2023

Assigning to @getsentry/support for routing ⏲️

@getsantry
Copy link
Contributor

getsantry bot commented Aug 31, 2023

Routing to @getsentry/product-owners-settings-integrations for triage ⏲️

@getsantry getsantry bot moved this from Waiting for: Support to Waiting for: Product Owner in GitHub Issues with 👀 Aug 31, 2023
@Dhrumil-Sentry
Copy link

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

@getsantry getsantry bot removed the status in GitHub Issues with 👀 Aug 31, 2023
@Dhrumil-Sentry Dhrumil-Sentry changed the title Jira issue creation silently fails when title is longer than 255 characters Sentry does not show Integration Errors- such as title length exceeded in Jira ticket creation Aug 31, 2023
@mikef-wildlight
Copy link

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.

@getsantry getsantry bot moved this to Waiting for: Product Owner in GitHub Issues with 👀 Aug 31, 2023
@getsantry getsantry bot removed the status in GitHub Issues with 👀 Aug 31, 2023
@linear linear bot added the Migrated label Jan 9, 2025
@Kobby-Bawuah
Copy link

Related to : https://sentry.zendesk.com/agent/tickets/144883

@getsantry getsantry bot moved this to Waiting for: Product Owner in GitHub Issues with 👀 3 Feb 12, 2025
@masinette
Copy link
Member

@rodolfoBee
Copy link
Member Author

Same issue was reported by a user on this ticket: https://sentry.zendesk.com/agent/tickets/145221

@rodolfoBee
Copy link
Member Author

@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.

@mikebollandajw
Copy link

mikebollandajw commented Feb 19, 2025

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?

Image

@sentaur-athena
Copy link
Member

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.

@bruno-garcia
Copy link
Member

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

@bruno-garcia
Copy link
Member

@GabeVillalobos does #85756 fix this issue? if so, can we close it?

@cobyeastwood183
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Archived in project
Development

Successfully merging a pull request may close this issue.