Summary must be less than 255 characters

[Shrikant Bhosale]

Is any solution or workaround to this for Jira Cloud.

[Alexey Matveev · Accepted solution]

Hello,

Summary must be less than 255 characters. You can not change it. Use the description field. Summary must be a short representation of your issue.

[Shrikant Bhosale]

@Alexey MatveevCould you please navigate me to the page where such limits are declared/posted.

[Alexey Matveev]

I ve never met such a limit in an official doc. But it is there.

[Dawid Krysiak]

Hi,
In my case it seems to be 100 characters and jira truncates the message to make sure that the front/end of the summary is visible, but replaces the content with '...'. Any ideas where to look for possible configuration issue?

Kind regards
Dawid

[Nic Brough -Adaptavist-]

You can't "fix" it because it's not broken.  You can't change it on Cloud (and I wouldn't try it on Jira Server because you'd have to rewrite the core code).

Text fields are limited by the code to match the smallest allowable text field in the standard databases (i.e. 254)

[Shrikant Bhosale]

@Nic Brough -Adaptavist-I want to know such limits.

[Nic Brough -Adaptavist-]

Why?  Your users won't remember, and if they go over them, the system will either not let them over-fill the field, or tell them they can't commit oversized strings.

But generally 254 and 32767 are the two limits for short and long text.

[Shrikant Bhosale]

Thanks @Nic Brough -Adaptavist-.

Actually I am migrating from Assembla to Jira with more than 10k tickets. That's why I want to know such limitations.

[Nic Brough -Adaptavist-]

Ok, you have the numbers now, so you know where to truncate or split any over-sized fields you are copying from Assembla!

[Payne]

As stated, the summary field limit cannot be modified, but the long text field (e.g. Description, Comments, etc.) length can be modified (at least in Jira server; not sure about Jira cloud) via the jira.text.field.character.limit setting, the default value being 32767.

[Dawid Krysiak]

I forgot about this thread completely.
I hope this helps other people.

The issue I was having was not caused by Jira, it was AWS SNS truncating the subject lines.
Looks like it's a legacy issue (mind you, SNS and SQS are the oldest technologies in AWS, predating AWS itself) that "they are working on" (read: don't hold your breath).
So if alarm name truncation is an issue for you, start developing your own solution using EventBridge and don't use SNS at all.