NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
I pasted in some HTML from an email bug report and was surprised to see the message below which I don't recall seeing in the past. I use MS SQL 2014, I would suggest description/comment fields (at least) use nvarchar(max) column properties to not be restricted.
The entered text is too long. It exceeds the allowed limit of 32767 characters.
Workaround:
If possible can include the contents of the multi line text field in a formatted text file and attach to the issue
- causes
-
JRACLOUD-64351 Provide a full solution for long comments breaching the character limit
- Gathering Interest
- is duplicated by
-
- Closed
- is related to
-
- Closed
-
- Gathering Interest
-
MOVE-97256 You do not have permission to view this issue
- relates to
-
- Closed
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JRACLOUD-59124] Allow description and comment fields unlimited text (no character limit)
Fully agree. Hitting this limit is a real inconvenience that should at least auto-truncate instead of throwing errors and ruining everything. Hope this is implemented soon.
4226c2412cb5 I do too agree/disagree with what you say. Peer review is not done in Jira comment section. Peer reviews are many times lengthy back and forth discussions, refrences, citations, benchmarks, argumentations and whatnot. An ordinary form field should not be used for that purpose. Fro that purpose you link that review to parallel epic, story, or an other type of issue you can think of, or even successive comments (which I have seen break like a glass 
). Jira was meant to be only developer's (not even engineer's) code and comment platform with rudimentary collaboration functions. Unfortunately people always want more of what Jira is not, and Atlassian makes some patches, repairs, but Jira is farther from its original concept becoming a Frankenstein's Creature.
While I understand where Zlatko is coming from on this. I do agree/disagree. Yes a file should be added as well; However Peer Reviewing a File in Jira Cloud is less than optimal. If you click wrong the file closes and you lose your place, refresh lose your place, etc. I feel that as an Engineer I put many details in a ticket that need to be reviewed; yes it can be done with separate comments however, that has it's own issues as well. I understand that the line length cannot be unlimited for all on a cloud product but it could at least be a bit larger. Also if they would not have removed support for scrollable textbox in Jira Comments with the {noformat} command I think line length wouldn't really be an issue as it wouldn't make the ticket a billion miles long and it would be contained in a box that scrolls like the Physical Server product.
If you need to cram 32K chars somewhere you need a file not a field.
Especially not a comment field. If you need 32K for a comment it is a documentation or a whole conversation not a brief and slim comment. Or you may have to work a bit on your writing skills.
Our organization is running into this as well, this character limit is Stone Age standards in the fast-paced environment of increasing complexity in technical auditing, standardizations, code/configurations & HTML overhead.
Unlimited seems unrealistic. Can it at least be doubled?
+1 Currently working on a description that's hitting the limit, probably thanks to bullets, table formatting and expand/contract...
Bump this please the ~32k char. limit is and absolute killer for developers and/or network engineers that have a lot of code/config. Jira Server was much better with handling this along with advanced formatting in comments like { code} and (noformat} where the long comments could be a scroll box. Going from Jira Server to Jira Cloud is a HUGE downgrade. .
The sibling ticket JRACLOUD-72176 has already 34 additional votes.
Also, part of the solution should be increasing the limit for custom fields of type Text
Increasing this value would be helpful for us too, as users of Jira cloud