NullPointerException when changing the Issue type when a multi pssf is configured

[Antonio Cerezo]

We're getting a NullPointer Exception error when the Issue type is changed and there is a custom field of type Project Specific Select Field (multi) configured.

Also when the Project Specific option is selected in the Project is displaying no options to set the field values.

I've attached what is logged when the error occurs. Any help to understand what could be the problem would be appreciated as in other instances is not happening.

Thanks

[Holger Schimanski]

Thanks for reporting! I am surprised to see this null pointer exception. Maybe a re-index i necessary because of a change of custom field context?

The stacktrace is from showing the "Project Specific" tab. Can you provide also provide a stacktrace from create resp. edit?

Best regards, Holger

[Holger Schimanski]

Can you also provide a screenshot of your custom field and the defined contexts?

Cheers, Holger

[Antonio Cerezo]

Hi Holger, thanks for looking into that so quickly. I already tried a re-index but that didn't fix it.

I've attached the stack trace of the NPE when a Issue is being created and the type is changed. There are also screenshots of the NPE, the field definition, the field configuration and the "Project Specific" tab.

Let me know if you need anything else.

Thanks, Antonio

[Holger Schimanski]

Very strange to see this error. If you look at pssf_npe_creating.txt all related Java classes are from JIRA... I want to check with you, that you not ran into a JIRA bug:

Which version of JIRA are you working with?

You wrote, that on other instances this problem does not occur. Do the other instances use a different JIRA version?

Can you please remove "CRO Area" custom field context, so that the custom field no longer is assigned to JIRA Sandpit. Try to create an issue for JIRA Sandpit. You should see no error message.

Now create a custom field "CRO Area 2" with JIRAs standard multi select field (and not Project Specific Multi Select Field) and configure it the same way with custom field context for JIRA Sandpit and also with no option value defined. And then try to create an issue for JIRA Sandpit. Do you get an error message now?

[Antonio Cerezo]

The version of JIRA is 6.0.1. I've done the steps you suggested to check if it's indeed a JIRA bug but with the CRO Area 2 plain Multi Select there are no errors.

[Holger Schimanski]

I am sorry, but I am not able to reproduce your problem. I have created a Project Specific Select Field or Project Specific Mulit Select Field (with no options) and created a context just for one project. I don't see any problems in create issue or in the Project Specific project tab.

You mentioned, that you have this problem only on one instance and others are okay. What are the differences between these instances.

Can you also use Integrity Checker to check your JIRA instance?

Can you also attach a screenshot of your Field Configuration of your project?

Kind regards, Holger

[Antonio Cerezo]

Hi Holger,

The other instance I was referring is a copy of the live environment where we are facing this issue. However, the data is not been synchronised for several months.

I've executed the Integrity Checker in both instances and both show some workflow entry errors. Do you think that could be affecting?

To avoid publishing information about our customer I'm sending you an email with the results of the Integrity Checker and the screenshot of the Field Configuration.

Thanks and regards, Antonio

[Ricksoft]

Hi Holger,

Our customer is also facing this issue. Is there any progress? Is this resolved in the latest version ?

Kind regards, Ricksoft.

[Holger Schimanski]

@atlassian5 I have problems to reproduce the bug. Therefor no fix is available at the moment.

Can you also enable detailed logging as described in the documentation and attach the logfile? Is the custom field configured for selected issue types only?

Many thanks, Holger

[Holger Schimanski]

Looks like being solved in recent versions. Closing this issue here, because now further reply from user and outdated.

If you see similar problem, please re-open or create new issue.