-
Notifications
You must be signed in to change notification settings - Fork 132
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
Gracefully handle issue description being too large. #41
Comments
From JRASERVER-64351. Though it appears like this limit can be increased when self-hosting. One solution, that should cover both cases would be:
|
Did it happen? :D |
Nope, help wanted. |
Thanks for ping 💪🏽 It indeed helped |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We got that because we put too much stuff on the JIRA issue while creating. The limit was around 32k chars. I feel like we could do better in Jiralert to truncate the description automatically if too large?
Want to start a discussion on it (:
The text was updated successfully, but these errors were encountered: