With a bigger table in the description I get a "It's too long for the field." error

[Thomas Werthmüller]

Hi

I try to update an issue with a bigger table in the description/comment and get always the error message:

We couldn't save your content

It's too long for the field. Try attaching a file or page to the issue, or adding part of the content as comments.

It's really strange, because the table contains not a lot of text, just 14 columns and 20 rows.

Has someone others also expected this problem or is there a known problem with tables that have a lot of rows?

It's a bit frustration, when I can't save prepared description.

Thanks,

Thomas

[Walter Buggenhout]

Hi @Thomas Werthmüller,

There is indeed a character limit of 32.767 characters for comment and description fields. Not only the text, but also the definition of the table is probably taking up space. While I can totally understand your frustration, in this specific case adding a file containing the table, a link to a Confluence page having that same table or any other reference to that table may be a feasible (and maybe even better) workaround. Jira is a very good work management tool, but not your best friend when your need is documentation. Once a ticket is completed, it gets hard to find if you need the described case again in the future (hence my reference to Confluence).

There is also a suggestion in the backlog to address this issue: you may want to watch JRACLOUD-59124 for future updates.

Hope this helps!

[Thomas Werthmüller]

Basically that's something only relevant for the issue/story, that's the reason I don't added it in a confluence page.

Fact is, that the text is only 2000 characters long, what means, that the table definition uses 30'000 characters? That confuses me.

[Thomas Werthmüller]

and thanks for your feedback @Walter Buggenhout !

[Garret Duffy]

Check for merged cells in the table.  I got this error when pasting a table (3 columns, 50 rows) from a google doc wherein I had merged columns in some rows as 'markers'. 

Once I split the those merged columns to match the rest of the table, it then pasted with no problems.

[Vinicius Sanches Guimarães]

I had this exact scenario, merged cells. Removing them from the table solved the problem. It really has nothing to do with the table taking space from the 32k char limit.

Thanks Garret!

[Torgny Hylen]

I also had this happen with merged cells. Character count ±6k but hit cap with two tables with 2 merged cells (so that the attached images flowed better with the data in the table). I also don't want to daisy chain documentation from one platform to another when it makes sense to keep everything about the ticket on the ticket. 

There's definitely room for some code optimisation on the implementation of tables. Something is very broken if its taking 24,000 characters to describe a few merged cells in a couple small tables (4x20).