The limit is not coded in many places, so it would not be that hard to find and amend the code that stops people entering it, but you are going to need to check every place where it might be used for assumptions, both the code that reads it and how a longer field will affect the UI

I would talk to the people who have given you broken requirements. There's a clue in the name of the field - "summary". It should be short and give the reader a rough idea. Many people would argue that 60 characters is too long, not too short. You should be telling the people with this "requirement" that they are wrong.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

If you spend enough time as a Jira admin - whether you are managing a single, mid-sized instance, a large enterprise one or juggling multiple instances at once - you will eventually find yourself in ...