Jira server issue not showing expected transitions
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
Symptom 1:
There are no transitions available in an issue, however there are other transitions in the workflow. Other issues from the same project can be transitioned.
Symptom 2:
There are no conditions in the workflow transition, the workflow is configured correctly, the user has the "Transition Issues" permission, reindexing the system and performing the integrity checker still does not cause the transition to show up.
Symptom 3:
A system workflow screen is missing from Jira. Depending on issue or projects, some issues will not show expected workflow transitions.
Cause
For Symptom 1:
The workflow entry of the issue has an incorrect state.
For Symptom 2:
There are workflow properties that exists in the Transition Properties. (Navigate to the missing transition's settings and click on View Properties in the UI)
For Symptom 3:
The following error is visible in the logs, when user is trying to transition the issue:
2024-04-16 12:08:23,194+0200 http-nio-8092-exec-984 url: /rest/api/2/issue/2320713/transitions; user: admin ERROR admin 728x6705294x20 1tlqiv5 192.168.1.10,192.168.1.9 /rest/api/2/issue/2320713/transitions [c.a.j.rest.exception.ExceptionInterceptor] Returning internal server error in response
java.lang.reflect.InvocationTargetException
at jdk.internal.reflect.GeneratedMethodAccessor4758.invoke(Unknown Source)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.base/java.lang.reflect.Method.invoke(Unknown Source)
at com.atlassian.plugins.rest.common.interceptor.impl.DispatchProviderHelper$ResponseOutInvoker.lambda$_dispatch$0(DispatchProviderHelper.java:181)
at com.atlassian.plugins.rest.common.interceptor.impl.DispatchProviderHelper.lambda$invokeMethodWithInterceptors$0(DispatchProviderHelper.java:81)
... 3 filtered
at com.atlassian.jira.rest.exception.ExceptionInterceptor.intercept(ExceptionInterceptor.java:55)
... 1 filtered
at com.atlassian.jira.rest.v2.issue.scope.RequestScopeInterceptor.intercept(RequestScopeInterceptor.java:39)
... 15 filtered
at com.atlassian.plugins.rest.module.RestDelegatingServletFilter$JerseyOsgiServletContainer.doFilter(RestDelegatingServletFilter.java:171)
... 1 filtered
at com.atlassian.plugins.rest.module.RestDelegatingServletFilter.doFilter(RestDelegatingServletFilter.java:75)
... 32 filtered
...
Caused by: java.lang.IllegalArgumentException: Cannot find Screen with id '2'.
at com.atlassian.jira.workflow.WorkflowActionsBean.getFieldScreenForView(WorkflowActionsBean.java:57)
...Workaround
For Cause 1:
Run the Integrity Checker (type "g"+"g" and search for integrity checker) in your JIRA to fix any broken relationships in your workflow.
Alternatively you may follow the steps from this page to manually find and fix workflow-related data issues directly in the database:
For Cause 2:
Delete the workflow properties and the transition should be appearing.
For Cause 3:
Follow the "Solution" section from the following article: Screens are not showing Workflow Association and can not delete unused screens in Jira
If this article does not addresses your problem, please raise a new case with Atlassian Support.