java.lang.RuntimeException: Error parsing meta attribute <meta name='jira.permission.work'>denied</meta>. Name format is 'jira.permission.[subtasks].<permission>.[group|user|assignee|...]'

Atlassian JIRA | Michael Ruflin [Atlassian] | 5 years ago
  1. 0

    Incorrect Exception message thrown, which misleads users. Also see https://jira.atlassian.com/browse/GHS-3325 The Exception thrown when entering a permission related workflow step variable looks like following: {code} java.lang.RuntimeException: Error parsing meta attribute <meta name='jira.permission.edit'>false</meta>. Name format is 'jira.permission.[subtasks].<permission>.[group|user|assignee|...]' [INFO] [talledLocalContainer] java.lang.RuntimeException: Error parsing meta attribute <meta name='jira.permission.edit'>false</meta>. Name format is 'jira.permission.[subtasks].<permission>.[group|user|assignee|...]' [INFO] [talledLocalContainer] at com.atlassian.jira.permission.WorkflowPermissionFactory.createWorkflowPermission(WorkflowPermissionFactory.java:81) [INFO] [talledLocalContainer] at com.atlassian.jira.permission.WorkflowPermissionFactory.getWorkflowPermissions(WorkflowPermissionFactory.java:41) [INFO] [talledLocalContainer] at com.atlassian.jira.security.WorkflowBasedPermissionManager.hasPermission(WorkflowBasedPermissionManager.java:75) {code} The user mistook the format (jira.permission.[subtasks].<permission>.[group|user|assignee|...]) for a pseudo regex, and thought subtask as well as the last part were optional, where only the subtask in fact is. According to the documentation http://confluence.atlassian.com/display/JIRA044/Workflow+Properties which links to http://docs.atlassian.com/software/jira/docs/api/latest/com/atlassian/jira/security/WorkflowBasedPermissionManager.html the correct format is 'jira.permission.[subtasks.]\{permission}.\{type}\[.suffix]' Please adapt the Exception message accordingly. *Scenario 2:* We have tested to add the workflow property and reproducible in JIRA 4.4.5, 5.0.7, 5.1.8 and 5.2.11: * jira.permission.work = denied It looks like the property is doing it's job, and the log work feature will be disable for that specific issue status. *Steps to reproduce* # Go to {{Administration > Workflows}} # Edit the related workflow, and create a draft workflow if required # Go to any of the workflow step (not transition!), open the property for that workflow step # Add the following property: {noformat} jira.permission.work = denied {noformat} *Finding:* Though the property seems to work, it looks like apparently we managed to reproduce the problem as well. In our test setup, the log work is disabled in the In Progress step due to the property, but when we try to resolve the issue, we get the following error: {noformat} 2013-05-23 22:24:21,341 http-bio-8081-exec-11 ERROR admin 1344x11961x1 1lif4su 0:0:0:0:0:0:0:1 /secure/IssueAction!default.jspa [atlassian.jira.permission.WorkflowPermissionFactory] Error parsing meta attribute <meta name='jira.permission.work'>denied</meta>. Name format is 'jira.permission.[subtasks].<permission>.[group|user|assignee|...]' 2013-05-23 22:24:21,342 http-bio-8081-exec-11 ERROR admin 1344x11961x1 1lif4su 0:0:0:0:0:0:0:1 /secure/IssueAction!default.jspa [atlassian.plugin.web.DefaultWebInterfaceManager] Could not evaluate condition 'com.atlassian.plugin.web.conditions.AndCompositeCondition@63e5635f' for descriptor: com.atlassian.jira.plugin.system.issueoperations:log-work (null) java.lang.RuntimeException: Error parsing meta attribute <meta name='jira.permission.work'>denied</meta>. Name format is 'jira.permission.[subtasks].<permission>.[group|user|assignee|...]' at com.atlassian.jira.permission.WorkflowPermissionFactory.createWorkflowPermission(WorkflowPermissionFactory.java:81) at com.atlassian.jira.permission.WorkflowPermissionFactory.getWorkflowPermissions(WorkflowPermissionFactory.java:41) at com.atlassian.jira.security.WorkflowBasedPermissionManager.hasPermission(WorkflowBasedPermissionManager.java:75) at com.atlassian.jira.security.AbstractPermissionManager.hasPermission(AbstractPermissionManager.java:113) at com.atlassian.jira.security.AbstractPermissionManager.hasPermission(AbstractPermissionManager.java:142) <+2> (DelegatingMethodAccessorImpl.java:25) {noformat}

    Atlassian JIRA | 5 years ago | Michael Ruflin [Atlassian]
    java.lang.RuntimeException: Error parsing meta attribute <meta name='jira.permission.work'>denied</meta>. Name format is 'jira.permission.[subtasks].<permission>.[group|user|assignee|...]'
  2. 0

    Incorrect Exception message thrown, which misleads users. Also see https://jira.atlassian.com/browse/GHS-3325 The Exception thrown when entering a permission related workflow step variable looks like following: {code} java.lang.RuntimeException: Error parsing meta attribute <meta name='jira.permission.edit'>false</meta>. Name format is 'jira.permission.[subtasks].<permission>.[group|user|assignee|...]' [INFO] [talledLocalContainer] java.lang.RuntimeException: Error parsing meta attribute <meta name='jira.permission.edit'>false</meta>. Name format is 'jira.permission.[subtasks].<permission>.[group|user|assignee|...]' [INFO] [talledLocalContainer] at com.atlassian.jira.permission.WorkflowPermissionFactory.createWorkflowPermission(WorkflowPermissionFactory.java:81) [INFO] [talledLocalContainer] at com.atlassian.jira.permission.WorkflowPermissionFactory.getWorkflowPermissions(WorkflowPermissionFactory.java:41) [INFO] [talledLocalContainer] at com.atlassian.jira.security.WorkflowBasedPermissionManager.hasPermission(WorkflowBasedPermissionManager.java:75) {code} The user mistook the format (jira.permission.[subtasks].<permission>.[group|user|assignee|...]) for a pseudo regex, and thought subtask as well as the last part were optional, where only the subtask in fact is. According to the documentation http://confluence.atlassian.com/display/JIRA044/Workflow+Properties which links to http://docs.atlassian.com/software/jira/docs/api/latest/com/atlassian/jira/security/WorkflowBasedPermissionManager.html the correct format is 'jira.permission.[subtasks.]\{permission}.\{type}\[.suffix]' Please adapt the Exception message accordingly. *Scenario 2:* We have tested to add the workflow property and reproducible in JIRA 4.4.5, 5.0.7, 5.1.8 and 5.2.11: * jira.permission.work = denied It looks like the property is doing it's job, and the log work feature will be disable for that specific issue status. *Steps to reproduce* # Go to {{Administration > Workflows}} # Edit the related workflow, and create a draft workflow if required # Go to any of the workflow step (not transition!), open the property for that workflow step # Add the following property: {noformat} jira.permission.work = denied {noformat} *Finding:* Though the property seems to work, it looks like apparently we managed to reproduce the problem as well. In our test setup, the log work is disabled in the In Progress step due to the property, but when we try to resolve the issue, we get the following error: {noformat} 2013-05-23 22:24:21,341 http-bio-8081-exec-11 ERROR admin 1344x11961x1 1lif4su 0:0:0:0:0:0:0:1 /secure/IssueAction!default.jspa [atlassian.jira.permission.WorkflowPermissionFactory] Error parsing meta attribute <meta name='jira.permission.work'>denied</meta>. Name format is 'jira.permission.[subtasks].<permission>.[group|user|assignee|...]' 2013-05-23 22:24:21,342 http-bio-8081-exec-11 ERROR admin 1344x11961x1 1lif4su 0:0:0:0:0:0:0:1 /secure/IssueAction!default.jspa [atlassian.plugin.web.DefaultWebInterfaceManager] Could not evaluate condition 'com.atlassian.plugin.web.conditions.AndCompositeCondition@63e5635f' for descriptor: com.atlassian.jira.plugin.system.issueoperations:log-work (null) java.lang.RuntimeException: Error parsing meta attribute <meta name='jira.permission.work'>denied</meta>. Name format is 'jira.permission.[subtasks].<permission>.[group|user|assignee|...]' at com.atlassian.jira.permission.WorkflowPermissionFactory.createWorkflowPermission(WorkflowPermissionFactory.java:81) at com.atlassian.jira.permission.WorkflowPermissionFactory.getWorkflowPermissions(WorkflowPermissionFactory.java:41) at com.atlassian.jira.security.WorkflowBasedPermissionManager.hasPermission(WorkflowBasedPermissionManager.java:75) at com.atlassian.jira.security.AbstractPermissionManager.hasPermission(AbstractPermissionManager.java:113) at com.atlassian.jira.security.AbstractPermissionManager.hasPermission(AbstractPermissionManager.java:142) <+2> (DelegatingMethodAccessorImpl.java:25) {noformat}

    Atlassian JIRA | 5 years ago | Michael Ruflin [Atlassian]
    java.lang.RuntimeException: Error parsing meta attribute <meta name='jira.permission.work'>denied</meta>. Name format is 'jira.permission.[subtasks].<permission>.[group|user|assignee|...]'
  3. 0

    Here is the scenario: # add new a status in JIRA (in my case "Validated") # copy the current workflow ("WFwithvalidation") and add the "Validated" status and add transitions to/from this new status # create a new workflow scheme, all issue types are associated to the new "WFwithvalidation" # migrate an existing project to the new workflow scheme: no status association necessary # create a new issue and apply transitions until the "Validated" status Then, the issue supposed to be in "Validated" cannot be opened - I got the "Oops System Error": {noformat} java.lang.RuntimeException: Could not find workflow status for issue VUGIS-634. at com.atlassian.jira.permission.PermissionContextImpl.getStatusGV(PermissionContextImpl.java:106) at com.atlassian.jira.permission.PermissionContextImpl.getRelevantStepDescriptor(PermissionContextImpl.java:83) at com.atlassian.jira.permission.WorkflowPermissionFactory.getWorkflowPermissions(WorkflowPermissionFactory.java:26) at com.atlassian.jira.security.WorkflowBasedPermissionManager.hasPermission(WorkflowBasedPermissionManager.java:73) at com.atlassian.jira.security.AbstractPermissionManager.hasPermission(AbstractPermissionManager.java:121) at sun.reflect.GeneratedMethodAccessor57.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.atlassian.util.profiling.object.ObjectProfiler.profiledInvoke(ObjectProfiler.java:71) at com.atlassian.jira.config.component.SwitchingInvocationHandler.invoke(SwitchingInvocationHandler.java:28) at $Proxy1.hasPermission(Unknown Source) at com.atlassian.jira.web.action.issue.AbstractIssueSelectAction.getIssue(AbstractIssueSelectAction.java:74) at com.atlassian.jira.web.action.issue.ViewIssue.doExecute(ViewIssue.java:156) at webwork.action.ActionSupport.execute(ActionSupport.java:153) 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:802) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672) at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:463) at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:398) at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:301) at com.atlassian.jira.servlet.QuickLinkServlet.service(QuickLinkServlet.java:58) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.atlassian.core.filters.HeaderSanitisingFilter.doFilter(HeaderSanitisingFilter.java:44) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.atlassian.jira.web.filters.AccessLogFilter.doFilter(AccessLogFilter.java:73) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.opensymphony.module.sitemesh.filter.PageFilter.parsePage(PageFilter.java:119) at com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.java:55) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.atlassian.seraph.filter.SecurityFilter.doFilter(SecurityFilter.java:204) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.atlassian.seraph.filter.TrustedApplicationsFilter.doFilter(TrustedApplicationsFilter.java:120) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.atlassian.seraph.filter.BaseLoginFilter.doFilter(BaseLoginFilter.java:138) at ro.softwin.elearning.jiratools.NTLMLoginFilter.doFilter(NTLMLoginFilter.java:127) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.atlassian.util.profiling.filters.ProfilingFilter.doFilter(ProfilingFilter.java:132) at com.atlassian.jira.web.filters.JIRAProfilingFilter.doFilter(JIRAProfilingFilter.java:16) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.atlassian.jira.web.filters.ActionCleanupDelayFilter.doFilter(ActionCleanupDelayFilter.java:43) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.atlassian.jira.web.filters.RequestCleanupFilter.doFilter(RequestCleanupFilter.java:50) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.atlassian.johnson.filters.AbstractJohnsonFilter.doFilter(AbstractJohnsonFilter.java:72) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.tuckey.web.filters.urlrewrite.UrlRewriteFilter.doFilter(UrlRewriteFilter.java:350) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.atlassian.gzipfilter.GzipFilter.doFilterInternal(GzipFilter.java:75) at com.atlassian.gzipfilter.GzipFilter.doFilter(GzipFilter.java:51) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.atlassian.core.filters.AbstractEncodingFilter.doFilter(AbstractEncodingFilter.java:33) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.atlassian.jira.appconsistency.db.DatabaseCompatibilityEnforcerFilter.doFilter(DatabaseCompatibilityEnforcerFilter.java:39) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.apache.catalina.valves.FastCommonAccessLogValve.invoke(FastCommonAccessLogValve.java:495) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684) at java.lang.Thread.run(Thread.java:619) {noformat} The atlassian-jira.log file only contains the stack trace ([500ErrorPage.jsp] Exception caught in 500 page Could not find workflow status for issu e VUGIS-634) and stack traces from IssueMailQueueItem.send failure with the same cause. Moreover, if I use new transitions to move an pre-existing issue (before workflow scheme migration) to "Validated", that issue has the same trouble too. I got the same trouble on my test system and then on my productive system, I have applied exactly the same process, except I have imported the workflow from XML into productive system. As the issue navigator does not display the new status (see Selection_019.png), I have tested a basic "re-index" on issues without success. Integrity Checker does not detect any trouble, see Selection_020.png. Database content seems perfectly correct, my issuestatus "Validated" has id 10008; I have used queries from http://confluence.atlassian.com/display/JIRA/Issue+status+and+workflow : {noformat} mysql> select issuestatus from jiraissue where pkey='VUGIS-634'; +-------------+ | issuestatus | +-------------+ | 10008 | +-------------+ 1 row in set (0.00 sec) mysql> select pname from issuestatus, jiraissue where issuestatus.id=jiraissue.issuestatus and pkey='VUGIS-634'; +-----------+ | pname | +-----------+ | Validated | +-----------+ 1 row in set (0.00 sec) mysql> select * from OS_WFENTRY where ID=(select workflow_id from jiraissue where pkey='VUGIS-634'); +-------+--------------------------------------+-------------+-------+ | ID | NAME | INITIALIZED | STATE | +-------+--------------------------------------+-------------+-------+ | 50392 | Standard 3 with validation v1.1 | NULL | 1 | +-------+--------------------------------------+-------------+-------+ 1 row in set (0.00 sec) mysql> select * from OS_CURRENTSTEP where ENTRY_ID=(select workflow_id from jiraissue where pkey='VUGIS-634'); +--------+----------+---------+-----------+-------+---------------------+----------+-------------+-----------+--------+ | ID | ENTRY_ID | STEP_ID | ACTION_ID | OWNER | START_DATE | DUE_DATE | FINISH_DATE | STATUS | CALLER | +--------+----------+---------+-----------+-------+---------------------+----------+-------------+-----------+--------+ | 158276 | 50392 | 10 | 0 | | 2011-03-22 18:50:44 | NULL | NULL | Validated | NULL | +--------+----------+---------+-----------+-------+---------------------+----------+-------------+-----------+--------+ 1 row in set (0.00 sec) {noformat} I have found the following workaround: # Shutdown JIRA # Startup JIRA, now the issue is displayed properly (no longer Oops System Error) but Issue Navigator still reports an empty status # re-index to fix the Issue Navigator display My guess: the "workflow permission" cache has not been invalidated after the workflow scheme migration and this trouble raised when a new status is added.

    Atlassian JIRA | 6 years ago | Yves Martin
    java.lang.RuntimeException: Could not find workflow status for issue VUGIS-634.
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    After importing a mantis project, the imported bugs with a custom status are not associated to any status. This results in the error below when trying to look at the details of such an issue. Instead, it should be possible to map an unknown status to an existing status, so that the issues can still be accessed afterwards. {quote} *Cause:* java.lang.RuntimeException: Could not find workflow status for issue AAA-1 *Stack Trace: [hide]* java.lang.RuntimeException: Could not find workflow status for issue AAA-1. at com.atlassian.jira.permission.PermissionContextImpl.getStatusGV(PermissionContextImpl.java:106) at com.atlassian.jira.permission.PermissionContextImpl.getRelevantStepDescriptor(PermissionContextImpl.java:83) at com.atlassian.jira.permission.WorkflowPermissionFactory.getWorkflowPermissions(WorkflowPermissionFactory.java:26) at com.atlassian.jira.security.WorkflowBasedPermissionManager.hasPermission(WorkflowBasedPermissionManager.java:71) at com.atlassian.jira.security.AbstractPermissionManager.hasPermission(AbstractPermissionManager.java:121) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.atlassian.util.profiling.object.ObjectProfiler.profiledInvoke(ObjectProfiler.java:71) at com.atlassian.jira.config.component.SwitchingInvocationHandler.invoke(SwitchingInvocationHandler.java:28) {quote}

    Atlassian JIRA | 10 years ago | Gino Marckx
    java.lang.RuntimeException: Could not find workflow status for issue AAA-1.
  6. 0

    The following situation results in an error with the issue view screen: * Workflow step has the property: {code} jira.permission.assign.issue: denied {code} * Issue does not have an assignee. Aka *unassigned* Viewing the issue results in ERROR in logs: {code} 2013-09-13 10:34:18,380 http-bio-8080-exec-1 ERROR sysadmin 634x150x1 1dgrvu3 0:0:0:0:0:0:0:1%0 /browse/TST-1 [atlassian.plugin.web.DefaultWebInterfaceManager] Could not evaluate condition 'com.atlassian.plugin.web.conditions.AndCompositeCondition@7009cc5' for descriptor: com.atlassian.jira.plugin.system.issueoperations:assign-to-me (null) java.lang.RuntimeException: Unknown type 'issue' in meta attribute 'jira.permission.assign.issue'. Valid permission types are defined in permission-types.xml at com.atlassian.jira.permission.WorkflowPermissionFactory.createWorkflowPermission(WorkflowPermissionFactory.java:81) at com.atlassian.jira.permission.WorkflowPermissionFactory.getWorkflowPermissions(WorkflowPermissionFactory.java:46) at com.atlassian.jira.security.WorkflowBasedPermissionManager.hasPermission(WorkflowBasedPermissionManager.java:75) at com.atlassian.jira.security.AbstractPermissionManager.hasPermission(AbstractPermissionManager.java:122) at com.atlassian.jira.security.AbstractPermissionManager.hasPermission(AbstractPermissionManager.java:151) at com.atlassian.jira.security.AbstractPermissionManager.hasPermission(AbstractPermissionManager.java:161) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.atlassian.util.profiling.object.ObjectProfiler.profiledInvoke(ObjectProfiler.java:83) at com.atlassian.jira.config.component.SwitchingInvocationHandler.invoke(SwitchingInvocationHandler.java:28) at com.sun.proxy.$Proxy79.hasPermission(Unknown Source) at com.atlassian.jira.plugin.webfragment.conditions.HasIssuePermissionCondition.shouldDisplay(HasIssuePermissionCondition.java:38) at com.atlassian.jira.plugin.webfragment.conditions.AbstractWebCondition.shouldDisplay(AbstractWebCondition.java:44) at com.atlassian.plugin.web.conditions.AndCompositeCondition.shouldDisplay(AndCompositeCondition.java:14) at com.atlassian.plugin.web.DefaultWebInterfaceManager.filterFragmentsByCondition(DefaultWebInterfaceManager.java:172) at com.atlassian.plugin.web.DefaultWebInterfaceManager.getDisplayableItems(DefaultWebInterfaceManager.java:103) at com.atlassian.jira.plugin.webfragment.JiraWebInterfaceManager.getDisplayableItems(JiraWebInterfaceManager.java:67) at com.atlassian.jira.plugin.webfragment.DefaultSimpleLinkManager.getLinksForSection(DefaultSimpleLinkManager.java:132) at sun.reflect.GeneratedMethodAccessor329.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.atlassian.plugin.osgi.hostcomponents.impl.DefaultComponentRegistrar$ContextClassLoaderSettingInvocationHandler.invoke(DefaultComponentRegistrar.java:129) at com.sun.proxy.$Proxy217.getLinksForSection(Unknown Source) at sun.reflect.GeneratedMethodAccessor329.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.atlassian.plugin.osgi.bridge.external.HostComponentFactoryBean$DynamicServiceInvocationHandler.invoke(HostComponentFactoryBean.java:154) at com.sun.proxy.$Proxy217.getLinksForSection(Unknown Source) at com.atlassian.jira.issue.util.IssueOperationsBarUtil.getPrimaryOperationLinks(IssueOperationsBarUtil.java:319) at com.atlassian.jira.rest.v2.issue.OpsbarBeanBuilder.buildOpsbarGroup(OpsbarBeanBuilder.java:90) at com.atlassian.jira.rest.v2.issue.OpsbarBeanBuilder.build(OpsbarBeanBuilder.java:59) at com.atlassian.jira.plugin.issuenav.IssueNavAction.doIssue(IssueNavAction.java:622) at com.atlassian.jira.plugin.issuenav.IssueNavAction.doDefault(IssueNavAction.java:263) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at webwork.util.InjectionUtils$DefaultInjectionImpl.invoke(InjectionUtils.java:70) at webwork.util.InjectionUtils.invoke(InjectionUtils.java:56) at webwork.action.ActionSupport.invokeCommand(ActionSupport.java:433) at webwork.action.ActionSupport.execute(ActionSupport.java:157) at com.atlassian.jira.action.JiraActionSupport.execute(JiraActionSupport.java:83) at webwork.interceptor.DefaultInterceptorChain.proceed(DefaultInterceptorChain.java:39) at webwork.interceptor.NestedInterceptorChain.proceed(NestedInterceptorChain.java:31) at webwork.interceptor.ChainedInterceptor.intercept(ChainedInterceptor.java:16) at webwork.interceptor.DefaultInterceptorChain.proceed(DefaultInterceptorChain.java:35) at webwork.dispatcher.GenericDispatcher.executeAction(GenericDispatcher.java:225) at webwork.dispatcher.GenericDispatcher.executeAction(GenericDispatcher.java:154) at com.atlassian.jira.web.dispatcher.JiraWebworkActionDispatcher.service(JiraWebworkActionDispatcher.java:151) at javax.servlet.http.HttpServlet.service(HttpServlet.java:722) at org.apache.catalina.core.ApplicationFilterChain.internalDoFil ... {code} Issue View screen shows: !issue-view-error.png|thumbnail! * There is no option to assign the issue to an user. h4. Workaround * Remove the *jira.permission.assign.issue* property from your workflow step.

    Atlassian JIRA | 3 years ago | David Chan [Atlassian]
    java.lang.RuntimeException: Unknown type 'issue' in meta attribute 'jira.permission.assign.issue'. Valid permission types are defined in permission-types.xml

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. java.lang.RuntimeException

      Error parsing meta attribute <meta name='jira.permission.work'>denied</meta>. Name format is 'jira.permission.[subtasks].<permission>.[group|user|assignee|...]'

      at com.atlassian.jira.permission.WorkflowPermissionFactory.createWorkflowPermission()
    2. com.atlassian.jira
      AbstractPermissionManager.hasPermission
      1. com.atlassian.jira.permission.WorkflowPermissionFactory.createWorkflowPermission(WorkflowPermissionFactory.java:81)
      2. com.atlassian.jira.permission.WorkflowPermissionFactory.getWorkflowPermissions(WorkflowPermissionFactory.java:41)
      3. com.atlassian.jira.security.WorkflowBasedPermissionManager.hasPermission(WorkflowBasedPermissionManager.java:75)
      4. com.atlassian.jira.security.AbstractPermissionManager.hasPermission(AbstractPermissionManager.java:113)
      4 frames