limit character on custom field

I have a text custom field and would like to limit it to 70 characters or less. Is there a way to do this so whenever this field is present on any screen it only allows 70 chars?

2 answers

1 accepted

1 vote
Accepted answer

Hello,

if you have Adaptivist Scriptrunner you can develop a behavior or validator. If you do not have Scriptrunner you can download JsIncluder plugin (https://marketplace.atlassian.com/plugins/ru.mail.jira.plugins.jsincluder/server/overview) and write custom javascript for create,  edit and view screen. 

Hello Alexey,

I currently use a regex validator in the workflow as follows:
[A-Z a-z 0-9 ,.-]{1,70}$

However I dont like this method. Also the error message is ugly (See attached).

 

char_limit.JPG

OK.  It s also a solution :)

I will also try it.  Thank you

Ok. Still looking for a better way to do it.

Found it here:https://community.atlassian.com/t5/Answers-Developer-Questions/How-to-set-a-length-size-on-a-custom-field-using-scriptrunner/qaq-p/554208

 

I am using behavior plugin

def field = getFieldByName("My Field Name")
if ((field?.value as String)?.length() > 70) {
field.setError("Length of the field should be less than 70 chars")
} else {
field.clearError()
}

Hello.  You can resolve this by adding a regular expression check to the workflow transition.  Much simpler than a groovy script.

 

Go to Project Setting > Workflows

Edit the workflow for the affected issue type

Switch to Diagram mode

On Create transition, click on the Validators

Choose Add Validator > Regular Expression Check

 

If you would like to restrict the field to a specific length:  enter [0-9]{n}$

 

(n) reflects your desired field length.

Neither of these options stop a user from changing the field AFTER doing the transition though as they both depend on a transition validation.

I was looking for something similar and it seems that if we can't absolutely stop a field EVER being longer than a certain length then there is little point restricting it SOMETIMES.

Ah, correction. It seems that BEHAVIOURS do apply at all times - looking into that now.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,618 views 18 21
Read article

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