We are trying to limit the amount of text that can be entered into the Summary and Description fields so that we do not need to read pages prior to finding out what the request is. This would be at the time of the request creation and possibly during editing through the transitions. Any thoughts?
Summaries are already short text, so 255 character max.
Description has no limit, and there's no way to cap it on Cloud yet (on server, you could do an ugly validator that would annoy your users by refusing to create or progress the issue until they'd shortened it, or use a behaviour or javascript, or even hack the html to limit it, etc)
Thanks for your response, Nic. 250 characters is WAY too much for our summaries. We are looking for Action items as a TITLE, with the short description to follow in the Description field. Even that, we don't want to read through a novella in order to find out what is needed. I guess this will become a STRONG TRAINING TOPIC. :-)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'm afraid so. I very rarely see issues that use anything like the 255 characters, they're usually half a dozen words at most, so I wouldn't expect you need to do a lot of training on that one. Description more so though...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You can achieve this by following these steps:
1. Go to the workflow and add a validation on the "Create" transition.
2. Add a validation via "Script Runner".
3. Use the following script:
issue.summary.split(' ').length >= 1 && issue.summary.split(' ').length <= 10
(Modify the number of words as per your requirement).
4. Test the script and add it.
5. Define a custom error message to help users understand the error.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.