what is the character limit for multiline text field in JIRA?

[Prasad Nagarale]

what is the character limit for multiline text field in JIRA?

[Ste Wright]

Hi @Prasad Nagarale 

According to one of our multi-line fields - 32,767 characters

@Ollie Guan beat me to this - but he's right, ours is limited to 32,767 (I assume this was a default).

You can modify the limit as a Jira Admin:

1. Jira Administration > System > General Configuration
2. Select the "Advanced Settings" button
3. Change the jira.text.field.character.limit

Ste

[Daniel David Smith]

Wrong chat sorry

[Ollie Guan]

Hi @Prasad Nagarale ,

The maximum is 2147483647.

https://confluence.atlassian.com/adminjiraserver/configuring-advanced-settings-938847828.html?_ga=2.263389068.1691819613.1597626978-1478559027.1570682324

[Bill Bill]

Not on Cloud :(

[Ste Wright]

Hi @Bill Bill 

It's set to 32,767 characters in Cloud - and is not editable.

You can vote for this to become configurable via JRACLOUD-63007 

Ste

[Goutham.P]

Hi @Ste Wright , 

Are there any Marketplace plugins available to solve this issue.

[Ste Wright]

Hi @Goutham.P 

Not that I've seen.

What scenario do you have with text which is longer than 32K characters? Could you use a linked Confluence page potentially?

Ste

[Alexey Solonenko]

@Ste Wright , good day,

From our side there are 3 issues:

1) Regulation and Audit about data. Many teams strongly prefer avoid any links to confluence, Excel, and to put all data for the ticket on the ticket. Any new system means more maintenance costs to govern access, and more risks for data-regulation and audits. 32k it s bit too little to put logs, tables, and proper descriptions. If I create a confluence page to support ticket, then how do I govern access? Which space? What about cross-team access? Jira already provides good mechanism, and there is a running cost for a team of admins to maintain it. If I add confluence, excel (sharepoint), draw.io - any other system multiplies costs and risks. If audit comes and finds that some content in confluence is not properly restricted - its a problem. At least having one system to manage - Jira, is easy. Separation of concerns.

2) Most teams favor comments vs. attachments because they are easily searchable with JQL. Its a life-saver during incidents and urgent bug-tracing.

3) Table editor randomly switches between markdown and html. Once its in html mode, you cannot even put a short list of users of a small team in 32k. Perhaps, a toggle would be good to have: "Im only in markdown mode - disable certain features, like cell merge" / "I'm in full mode - enable al features"

BR,

Alexey