Planning Board not accessible due to an InvocationException thrown by method 'canEdit'

Still need help?

The Atlassian Community is here for you.

Ask the community


Planning Board is not accessible due to a rendering error. The stack trace indicates that this is thrown by method canEdit and the following appears in the log files:

	at com.atlassian.jira.workflow.SimpleWorkflowManager.isEditable(
	at com.atlassian.jira.issue.managers.DefaultIssueManager.isEditable(
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(
	at java.lang.reflect.Method.invoke(


This error is caused by one or more issues which have an associated status that is no longer mapped with the current project workflow. The following bug report is related with this problem: JRA-19556 - Getting issue details... STATUS


We will need to find what issues are mapped to an incorrect status and then, clone or delete them:

  1. Run the Database Integrity Checker. It should identify the culprit and show an error like the one below:

    UNFIXABLE ERROR: The issue with key TEST-1234 has a status of Test Status which is not a valid status for the issues workflow, contact Atlassian support to resolve this problem.(JRA-8326)
  2. The affected issues need to be deleted. If you will need to keep their content, you can clone them and then, delete the original ones.

  3. Run the Re-index (Administration -> System -> Indexing). Please note that your instance will be unavailable while the re-index runs.
Last modified on Nov 15, 2018

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.