No Command 'configureOption' in Action Due to JIRA Database Values Plugin
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. 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
This problem is related to a third party plugin, and therefore not supported by Atlassian. See Atlassian Supported Plugins for more information.
Symptoms
Reordering a custom field value option throws an exception:
1
2
3
4
5
6
7
java.lang.IllegalArgumentException: No command 'configureOption' in action
at webwork.action.ActionSupport.invokeCommand(ActionSupport.java:413)
at webwork.action.ActionSupport.execute(ActionSupport.java:146)
at com.atlassian.jira.action.JiraActionSupport.execute(JiraActionSupport.java:54)
at webwork.dispatcher.GenericDispatcher.executeAction(GenericDispatcher.java:132)
at com.atlassian.jira.web.dispatcher.JiraServletDispatcher.service(JiraServletDispatcher.java:178)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
Cause
The problem is caused by the database values option plugin.
Resolution
Check the plugin's issue tracker for a resolution. This particular issue is tracked here.
Was this helpful?