Transition validation: missing entries not indicated on tabs

Question

I am working on Jira server 7.13.5.

In Jira workflow transition validation, I have 4 tabs in transition screen.

When I execute transition , missing entries from transition screen tab 2 or 3 or 4 are not highlighted and stays on default tab in transition screen.

Missing entries have to be found by clicking through the tabs.

Please let me know if any one faced such issue and resolved it.

Thanks in advance.

Devendra Patidar · Answer

Hi @Andy Heinzer ,

Thanks for your quick response.

I found the root cause of issue. It is because of behaviour and current version of Scriptrunner plugin. You can find the bug raised with plugin.

https://productsupport.adaptavist.com/browse/SRJIRA-4332

Regards,

Devendra

Andy Heinzer · Answer

Hi Devendra,

I understand that you are using some kind of workflow validator and are expecting Jira to better highlight these workflow validation failures when they are happening across multiple tabs in a transition screen.

I would like to try to better understand this problem.  In my own testing so far, I find that Jira Server does not really offer much in the way of validators, just a simple user permissions validator.  Could you let me know which add-on/plugin you are using in Jira Server in order to add a validator here?  If you're not sure, then perhaps you can take a closer look at the workflow editor to see what validator options are available there. Alternatively, if you are a system administrator, you could take a look at the Manage Apps or Manage Addons page.  You can find this by going to the Gear Icon -> Manage Apps (although in your version it might still be called Manage Add-ons).

I tried to recreate this problem using the Workflow Magic Box plugin to provide a bunch of different validators.  While I was able to recreate what I believe is the problem you are reporting here, I also found that the validator error message seems dependent upon the add-on more-so than Jira itself.  So it might be a factor here in regards to how Jira behaves here.  Given that Jira Server does not exactly have many validator options natively, it makes it harder to determine what is exactly the expected behavior here given your configuration.  Certainly the transition is being prevented, so in at least one sense this is working as designed.  However I can certainly empathize here and I understand why you would want this to work a bit differently so that the end users can more clearly and easily understand which field(s) are preventing this transition from going through.

Perhaps if I can learn more about your setup and configuration here, I can investigate this further.

Andy