Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-15307

Configuring a board's Issue Details View to include custom fields with specific issue type contexts causes SafePluginPointAccess errors in the logs

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Fix
    • Icon: High High
    • None
    • 7.2.3, 7.2.7, 7.3.0, 7.3.1, 7.3.4, 7.3.6, 7.4.1, 7.4.4, 7.5.0, 7.6.2, 7.6.3, 7.6.4, 7.6.6, 7.7.1, 7.8.0, 7.8.1, 7.8.2, 7.10.1, 7.10.2, 7.11.1, 7.12.1, 8.20.0
    • Board configuration
    • 7.02
    • 73
    • Severity 3 - Minor
    • 28
    • Hide
      Atlassian Update – 7 April 2025

      Dear Customers,

      Thank you for submitting this bug.
      Our strategy is to keep Data Center products secure, compliant, and performant while enabling customers to benefit from the innovation in Atlassian Cloud by investing in cloud connectors. Those are key drivers in prioritizing bug fixes.
      Although we understand that this bug is important to you we are closing it now as this is not aligned with our strategy. You can read more about our bug fix policy here and how we prioritize bugs.

      Workaround for this bug can be found in the description of this issue. 
      Best regards

      Daniel Dudziak
      Principal Software Engineer

      Show
      Atlassian Update – 7 April 2025 Dear Customers, Thank you for submitting this bug. Our strategy is to keep Data Center products  secure, compliant, and performant  while enabling customers to benefit from the innovation in Atlassian Cloud by investing in  cloud connectors.  Those are key drivers in prioritizing bug fixes. Although we understand that this bug is important to you we are closing it now as this is not aligned with our strategy. You can read more about  our bug fix policy here  and how we prioritize bugs. Workaround for this bug can be found in the description of this issue.  Best regards Daniel Dudziak Principal Software Engineer

      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

      1. Configure a new JIRA KANBAN board. With the filter set to one particular project
      2. Create a custom field called 'Test'
      3. Set the context for the field for 'Bug' issue type only
      4. Go to the Board's configuration > Issue Detail View and add this field
      5. Create a new issue on the board, with Task issue type
      6. 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.

              Unassigned Unassigned
              amasut Azfar Masut (Inactive)
              Votes:
              217 Vote for this issue
              Watchers:
              162 Start watching this issue

                Created:
                Updated:
                Resolved: