Unable to create JIRA issue: 'Error creating issue: Cannot invoke method getValidators() on null object'

[Karthik Bhat]

Hi,

I have been using Behaviours plugin for some projects in JIRA and I have made sure that this wont affect the default jira workflow for other projects. But when I try to create a JIRA issue for one of the projects not having any behaviour, I get this error message:

Error creating issue: Cannot invoke method getValidators() on null object

I have tried to reindex the custom fields and I am not able to do that as well.

2013-01-07 03:28:39,468 JiraTaskExectionThread-1 ERROR admin 208x15880x1 19tii9n 192.168.117.51 /secure/admin/jira/IndexReIndex.jspa [jira.util.index.CompositeIndexLifecycleManager] Reindex All FAILED. Indexer: DefaultIndexManager: paths: [/var/atlassian/application-data/jira/caches/indexes/comments, /var/atlassian/application-data/jira/caches/indexes/issues, /var/atlassian/application-data/jira/caches/indexes/changes]
java.lang.RuntimeException: java.util.concurrent.ExecutionException: java.lang.NullPointerException: Cannot invoke method getValidators() on null object

Could someone please help?

[JamieA · Accepted solution]

Didn't you already ask this and I asked you to provide some more information? What version of the behaviours plugin are you using? Old versions with hidden fields could cause this problem.

Possibly you have a hidden field that is associated with this project, but no behaviour? I could see that might be an issue, although it would be a bug if so. If so make sure the hidden field is only associated with projects that have a behaviour mapped.

[Karthik Bhat]

Hi Jamie,

I think you are referring to this question:

https://answers.atlassian.com/questions/112875/why-am-i-getting-an-error-related-to-the-behaviour-plugin

I am using JIRA 5.2 and Behaviours 0.5.3.

The project in which I am trying to create an issue is not having any hidden fields and all fields in this projects are default JIRA fields. The mapping in my behaviours do not apply for this project.

[JamieA]

Hi...

Do you have any custom fields of type "hidden text field" or hiddne number field?

> https://answers.atlassian.com/questions/112875/why-am-i-getting-an-error-related-to-the-behaviour-plugin

Yes, and you've asked another one. Please answer my questions rather than creating new questions.

If you can't do that then please just disable the behaviours plugin and your problem will go away.

[Karthik Bhat]

I had 2 custom fields which were of type 'Hideable Free Text Field (unlimited text)'. Now I have deleted them both. I am able to create issue now. But the Search Navigator does not show any issues. Let me try reindexing again.

[Karthik Bhat]

Reindexing worked. I am able to see the issues now through issue navigator.

[Karthik Bhat]

Hi Jamie,

I did not know that the 2 problems(Issue navigator returning empty results and unable to create new issue) might be related to each other. Hence I had created 2 questions. Thanks a ton for helping me out here.

Another question related to behaviours plugin I had was: Can behaviours be made to work even during bulk edit?

[JamieA]

Great, glad that is solved. I think you have asked about bulk edit elsewhere... I was going to answer that question more fully when I get a minute. There is an issue in the issue tracker which discusses why this is not possible. In short, you can't do it. If you have business critical logic that must be followed then you need to back it up with jira workflow validator functions.

[Karthik Bhat]

Sure. That would be one way to do it. Yes, I had asked this question in behaviours confluence page. Thanks a lot Jamie!

[Cristian _Southend_]

I had the same error. I solved the problem by mapping the field in the configuration of the new behaviour

[Higashi]

Could you paste here part of your workflow XML between <validators> </validators> tag ?

for example:

<validators>
        <validator name="" type="class">
          <arg name="class.name">com.atlassian.jira.workflow.validator.PermissionValidator</arg>
          <arg name="permission">Create Issue</arg>
        </validator>
</validators>

If using non-atlassian validators, you could try upgrading plugin that is responsible for it or change validator to some different one.

[Yilin]

Are you using a third part plugin to provide a validator in your workflow (most likely in the condition of the open transaction)? if this is the case, it could be that plugin is not enable which cause this problem.