Default length of text field(multiline)

can you please let me know the length of string that the description or text field(multiline) field currently supports?

9 answers

This widget could not be displayed.

After researching I found the answer Atlassian OnDemand uses Postgresql https://confluence.atlassian.com/cloud/database-and-ip-information-744721662.html.
The limitation for Postgresql text fields is approximately 1 GB. http://www.postgresql.org/docs/8.4/static/datatype-character.html
Hope this helps Arjun.

Thanks and Regards,
Tyler Borg

It are unconfirmed assumptions. There should be official documentation for this.

This widget could not be displayed.

In useful terms, "big enough".  It can hold more text than any human would find readable.

This widget could not be displayed.

I understand you must not be a technical user so this won't make sense to you but I am designing an internal database that we transfer data from the JIRA CLOUD API, and when I make SQL table columns they want an exact length. Big Enough is not a valid size for a nvarchar column. For purposes of data storage and compatibility in the data transfer application exact length is a very essential piece of information.

This widget could not be displayed.

I also need an answer to this question in the form of a specific length.

This widget could not be displayed.

Why? It's utterly useless information because over-large text fields are useless to you.

This widget could not be displayed.

I'm technical enough to understand that, but the answer is still "big enough". What you're trying to do is limit something that you don't know to a number you can't know. The really simple answer is that you have to assume 2^32-1 bytes, because the field is technically only limited by the size of the database field. (Oh, I'm also technical enough to point out that someone is probably doing something very wrong if they are asking you for "an exact length". It strongly implies someone has done a database introduction course and not quite got it)

This widget could not be displayed.

Nearly. What I'm trying to say is that trying to put a number on it is pointless. 4000 isn't enough, I know of many systems that have gone over that. But equally, you won't find systems that use the *physical* limit because humans simply won't enter 65-ish copies of the world's best-selling book (uncompressed), you can be pretty sure they won't read all of it, and the web-server is likely to time-out before rendering it all. But you can't guarantee where it will land between " a couple of words" and "a long rambling description of something". So, yet again, I have to say "don't limit it". It's the wrong thing to do, and it's simply not necessary in any modern database anyway.

This widget could not be displayed.

@Nic Brough [Adaptavist] as an add-on developer I have to know such information to apply these limits to the data which was provided by my add-on and is going to be saved into the standard custom field.

This widget could not be displayed.

Same answer applies.  If your add-on is dumping over-large data into a field, it's a complete waste of time and you're doing the wrong thing.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted yesterday in Jira

What modern development practices are at the heart of how your team delivers software?

Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...

50 views 0 1
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you