Jira Software Agile board throws Error No value present when viewing issue details
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Problem
When attempting to access the Issue Detail View on an Agile board, the view does not load and instead presents an "Error No value present":
The following appears in the atlassian-jira.log:
Uncaught exception thrown by REST service: No value present
java.util.NoSuchElementException: No value present
at java.util.Optional.get(Unknown Source)
at com.atlassian.greenhopper.web.contextprovider.issuedetailsview.CommentBlockContextProviderWrapper.extractCommentTabPanel(CommentBlockContextProviderWrapper.java:82)
Diagnosis
Environment
The issue is reproducible with all installed apps disabled by entering Safe Mode.
Diagnostic Steps
Check the pluginstate table:
select * from pluginstate
If you have the following entry, the resolution outlined in this document is applicable for your JIRA instance:
+--------------------------------------------------------------------+---------------+
| pluginkey | pluginenabled |
+--------------------------------------------------------------------+---------------+
| com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel | false |
Cause
The issuetabpanels:comment-tabpanel
has been disabled and needs to be re-enabled in order to display comments in the Issue Detail View.
Resolution
Always back up your data before performing any modification to the database. If possible, try your modifications on a test server.
- Stop Jira.
Login to the Jira DB and run the following SQL query:
delete from pluginstate where pluginkey='com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel';
- Restart Jira
- Verify if the problem has been resolved.
If any of the above steps did not help, please raise an issue with Atlassian Support with a Support Zip from your instance.