Details
-
Bug
-
Resolution: Unresolved
-
High
-
None
-
7.3.0, 7.2.3, 7.2.7, 7.3.1, 7.3.6, 7.4.1, 7.4.4, 7.5.0, 7.6.2, 7.6.3, 7.6.4, 7.7.1, 7.8.0, 7.8.1, 7.3.4, 7.8.2, 7.6.6, 7.10.1, 7.10.2, 7.11.1, 7.12.1, 8.20.0
-
7.02
-
67
-
Severity 3 - Minor
-
26
-
-
Description
Summary
If you configured your custom field context to only certain specific issue type, and you configure the Agile Board's 'Issue Details View' to call this custom field, c.atlassian.ozymandias.SafePluginPointAccess will be throwing error
Steps to Reproduce
- Configure a new JIRA KANBAN board. With the filter set to one particular project
- Create a custom field called 'Test'
- Set the context for the field for 'Bug' issue type only
- Go to the Board's configuration > Issue Detail View and add this field
- Create a new issue on the board, with Task issue type
- On the board, click on the issue to trigger the right details issue view panel
Expected Results
No error is thrown in the logs
Actual Results
Below exception is thrown in the atlassian.log file:
/rest/greenhopper/1.0/xboard/issue/details.json [c.atlassian.ozymandias.SafePluginPointAccess] Unable to run plugin code because of 'com.atlassian.jira.util.dbc.Assertions$NullArgumentException - config should not be null!'. com.atlassian.jira.util.dbc.Assertions$NullArgumentException: config should not be null! at com.atlassian.jira.util.dbc.Assertions.notNull(Assertions.java:25) at com.atlassian.jira.plugin.customfield.CustomFieldTypeModuleDescriptorImpl$2.call(CustomFieldTypeModuleDescriptorImpl.java:175) at com.atlassian.jira.plugin.customfield.CustomFieldTypeModuleDescriptorImpl$2.call(CustomFieldTypeModuleDescriptorImpl.java:172) at com.atlassian.ozymandias.SafePluginPointAccess.call(SafePluginPointAccess.java:187) at com.atlassian.jira.plugin.customfield.CustomFieldTypeModuleDescriptorImpl.getSupplierValueOrHtmlErrorMessage(CustomFieldTypeModuleDescriptorImpl.java:372) at com.atlassian.jira.plugin.customfield.CustomFieldTypeModuleDescriptorImpl.getEditHtml(CustomFieldTypeModuleDescriptorImpl.java:172) at com.atlassian.jira.issue.fields.ImmutableCustomField.getEditHtml(ImmutableCustomField.java:889) at com.atlassian.greenhopper.web.rapid.view.detailview.DetailViewInlineEditableFieldFactory.getFieldHtmlBean(DetailViewInlineEditableFieldFactory.java:263) at com.atlassian.greenhopper.web.rapid.view.detailview.DetailViewInlineEditableFieldFactory.lambda$getDetailViewEditableFields$54(DetailViewInlineEditableFieldFactory.java:162) at java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193)
Notes
This is not impacting any functionality. Just on logging
Workaround
Jira Administrators can hide logging on the package by increasing logging level to ERROR.
You can achieve this by adding these lines into log4j.properties:
log4j.logger.com.atlassian.ozymandias = ERROR, console, filelog
log4j.additivity.com.atlassian.ozymandias = false
For changes to make an effect, Jira restart is required.
The file log4j.properties is located at JIRA_INSTALL_DIR/atlassian-jira/WEB-INF/classes (as of Jira 7.12.x)
Mind, this would make the log lines disappear, yet would not address the root cause.
The actual case had to be addressed by the plug-in vendor.
Attachments
Issue Links
- is related to
-
JSWSERVER-16374 [c.atlassian.ozymandias.SafePluginPointAccess] Unable to run plugin code because of 'java.lang.NullPointerException - name argument cannot be null'.
- Closed
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
- relates to
-
FLASH-3938 Loading...
-
FLASH-3702 Loading...