nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

field validation plugin

Fabio Catalano

Hi,

I have a very old jira version Jira 3.13.5 According your experience which is the best plugin to perform field validation controls? I was trying behaviour and groovy plugin but they do not work properly. "Behaviour plugin" is working just for making a field mandatory (other functionalities do not work), "groovy plugin" it's working but when I set the error custom message i get a generic "error creating issue"

Accepted answers

Nic Brough -Adaptavist-

It depends on the validation you need.

Behaviours and the Scripting plugin are very useful and do work well on Jira 3.13 (there's no information here to help us debug your issue creation - have a look at the log file). You could also try other plugins from the marketplace that provide validators, or even write your own validators for the workflow transitions. Look for Jira Suite utilities and Misc Workflow extensions as a start.

For all of this though, it is well worth checking that you are using the correct versions of the plugins for Jira 3.13...

All comments

Nic Brough -Adaptavist-

It depends on the validation you need.

For all of this though, it is well worth checking that you are using the correct versions of the plugins for Jira 3.13...

Nic Brough -Adaptavist-

Difficult to tell from that. Either the version of the plugin is wrong, or it's configured to validate something it can't, or it's a bug.

Maybe share what you've set up on this validator as well?

Fabio Catalano

Hi Nic, thanks for your response. I can guve you a portion of the log file of today activities. Please see attached file: (catalina.Part.out.txt)

Renjith Pillai

Fabio, it is really an old version. Try moving to a newer versions and I promise you, you will love the new releases.

Fabio Catalano

It is just the mandatory field validation by using the post function workflow control. I expect to see the error message I set up but i just see a generic error with no information

Fabio Catalano

Yes I 'know but I have many constraint related to customization done during the past years that make difficult to upgrade without a big impact on our processes

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-administration