java.lang.RuntimeException: Unknown type 'clone' in meta attribute 'jira.permission.create.clone.denied'. Valid permission types are defined in permission-types.xml

Atlassian JIRA | Woo Yit Wei [Atlassian] | 1 year ago
tip
Click on the to mark the solution that helps you, Samebug will learn from it.
As a community member, you’ll be rewarded for you help.
  1. 0

    h3. Summary When a user adds {{jira.permission.create.clone.denied}} in a workflow property, running the *[Get create issue meta|https://docs.atlassian.com/jira/REST/latest/#api/2/issue-getCreateIssueMeta]* with _expand=projects.issuetypes.fields_ fail {code}http://localhost:8080/jira/rest/api/latest/issue/createmeta?expand=projects.issuetypes.fields{code} I understand that this is an incorrect usage of the property (JRA-34816), but the reason this Bug is raised is because workflow properties seems unrelated to metadata for creating issues. Adding workflow properties should not break an unrelated part of JIRA h3. Steps to Reproduce # Add {{jira.permission.create.clone.denied}} in a workflow property of a Status # Verify that users won't be able to clone issues in that particular status # Run [Get create issue meta|https://docs.atlassian.com/jira/REST/latest/#api/2/issue-getCreateIssueMeta] h3. Expected Results # The metadata should be returned normally h3. Actual Results # The below exception is thrown as a response {noformat}<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <status> <status-code>500</status-code> <message>Unknown type 'clone' in meta attribute 'jira.permission.create.clone.denied'. Valid permission types are defined in permission-types.xml</message> <stack-trace>java.lang.RuntimeException: Unknown type 'clone' in meta attribute 'jira.permission.create.clone.denied'. Valid permission types are defined in permission-types.xml at com.atlassian.jira.permission.WorkflowPermissionFactory.createWorkflowPermission(WorkflowPermissionFactory.java:86) at com.atlassian.jira.permission.WorkflowPermissionFactory.getWorkflowPermissions(WorkflowPermissionFactory.java:42) at com.atlassian.jira.security.WorkflowBasedPermissionManager.workflowPermissionCheck(WorkflowBasedPermissionManager.java:196) at com.atlassian.jira.security.WorkflowBasedPermissionManager.workflowPermissionCheck(WorkflowBasedPermissionManager.java:172) at com.atlassian.jira.security.WorkflowBasedPermissionManager.workflowPermissionCheck(WorkflowBasedPermissionManager.java:137) at com.atlassian.jira.security.WorkflowBasedPermissionManager.hasPermission(WorkflowBasedPermissionManager.java:83) at com.atlassian.jira.security.DefaultPermissionManager.hasPermission(DefaultPermissionManager.java:103) at com.atlassian.jira.security.WorkflowBasedPermissionManager.hasPermission(WorkflowBasedPermissionManager.java:76) at com.atlassian.jira.security.ApplicationRequiredPermissionManager.lambda$hasPermission$235(ApplicationRequiredPermissionManager.java:71) at com.atlassian.jira.security.ApplicationRequiredPermissionManager$$Lambda$365/587147594.getAsBoolean(Unknown Source) at com.atlassian.jira.security.ApplicationRequiredPermissionManager.checkUserHasApplicationOrFalse(ApplicationRequiredPermissionManager.java:177) at com.atlassian.jira.security.ApplicationRequiredPermissionManager.hasPermission(ApplicationRequiredPermissionManager.java:71) at sun.reflect.GeneratedMethodAccessor392.invoke(Unknown Source){noformat} # Results are returned when *expand=projects.issuetypes.fields* is removed, but this doesn't return the required data h3.Workaround No known workaround

    Atlassian JIRA | 1 year ago | Woo Yit Wei [Atlassian]
    java.lang.RuntimeException: Unknown type 'clone' in meta attribute 'jira.permission.create.clone.denied'. Valid permission types are defined in permission-types.xml
  2. 0

    h3. Summary When a user adds {{jira.permission.create.clone.denied}} in a workflow property, running the *[Get create issue meta|https://docs.atlassian.com/jira/REST/latest/#api/2/issue-getCreateIssueMeta]* with _expand=projects.issuetypes.fields_ fail {code}http://localhost:8080/jira/rest/api/latest/issue/createmeta?expand=projects.issuetypes.fields{code} I understand that this is an incorrect usage of the property (JRA-34816), but the reason this Bug is raised is because workflow properties seems unrelated to metadata for creating issues. Adding workflow properties should not break an unrelated part of JIRA h3. Steps to Reproduce # Add {{jira.permission.create.clone.denied}} in a workflow property of a Status # Verify that users won't be able to clone issues in that particular status # Run [Get create issue meta|https://docs.atlassian.com/jira/REST/latest/#api/2/issue-getCreateIssueMeta] h3. Expected Results # The metadata should be returned normally h3. Actual Results # The below exception is thrown as a response {noformat}<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <status> <status-code>500</status-code> <message>Unknown type 'clone' in meta attribute 'jira.permission.create.clone.denied'. Valid permission types are defined in permission-types.xml</message> <stack-trace>java.lang.RuntimeException: Unknown type 'clone' in meta attribute 'jira.permission.create.clone.denied'. Valid permission types are defined in permission-types.xml at com.atlassian.jira.permission.WorkflowPermissionFactory.createWorkflowPermission(WorkflowPermissionFactory.java:86) at com.atlassian.jira.permission.WorkflowPermissionFactory.getWorkflowPermissions(WorkflowPermissionFactory.java:42) at com.atlassian.jira.security.WorkflowBasedPermissionManager.workflowPermissionCheck(WorkflowBasedPermissionManager.java:196) at com.atlassian.jira.security.WorkflowBasedPermissionManager.workflowPermissionCheck(WorkflowBasedPermissionManager.java:172) at com.atlassian.jira.security.WorkflowBasedPermissionManager.workflowPermissionCheck(WorkflowBasedPermissionManager.java:137) at com.atlassian.jira.security.WorkflowBasedPermissionManager.hasPermission(WorkflowBasedPermissionManager.java:83) at com.atlassian.jira.security.DefaultPermissionManager.hasPermission(DefaultPermissionManager.java:103) at com.atlassian.jira.security.WorkflowBasedPermissionManager.hasPermission(WorkflowBasedPermissionManager.java:76) at com.atlassian.jira.security.ApplicationRequiredPermissionManager.lambda$hasPermission$235(ApplicationRequiredPermissionManager.java:71) at com.atlassian.jira.security.ApplicationRequiredPermissionManager$$Lambda$365/587147594.getAsBoolean(Unknown Source) at com.atlassian.jira.security.ApplicationRequiredPermissionManager.checkUserHasApplicationOrFalse(ApplicationRequiredPermissionManager.java:177) at com.atlassian.jira.security.ApplicationRequiredPermissionManager.hasPermission(ApplicationRequiredPermissionManager.java:71) at sun.reflect.GeneratedMethodAccessor392.invoke(Unknown Source){noformat} # Results are returned when *expand=projects.issuetypes.fields* is removed, but this doesn't return the required data h3.Workaround No known workaround

    Atlassian JIRA | 1 year ago | Woo Yit Wei [Atlassian]
    java.lang.RuntimeException: Unknown type 'clone' in meta attribute 'jira.permission.create.clone.denied'. Valid permission types are defined in permission-types.xml

    Root Cause Analysis

    1. java.lang.RuntimeException

      Unknown type 'clone' in meta attribute 'jira.permission.create.clone.denied'. Valid permission types are defined in permission-types.xml

      at com.atlassian.jira.permission.WorkflowPermissionFactory.createWorkflowPermission()
    2. com.atlassian.jira
      ApplicationRequiredPermissionManager.lambda$hasPermission$235
      1. com.atlassian.jira.permission.WorkflowPermissionFactory.createWorkflowPermission(WorkflowPermissionFactory.java:86)
      2. com.atlassian.jira.permission.WorkflowPermissionFactory.getWorkflowPermissions(WorkflowPermissionFactory.java:42)
      3. com.atlassian.jira.security.WorkflowBasedPermissionManager.workflowPermissionCheck(WorkflowBasedPermissionManager.java:196)
      4. com.atlassian.jira.security.WorkflowBasedPermissionManager.workflowPermissionCheck(WorkflowBasedPermissionManager.java:172)
      5. com.atlassian.jira.security.WorkflowBasedPermissionManager.workflowPermissionCheck(WorkflowBasedPermissionManager.java:137)
      6. com.atlassian.jira.security.WorkflowBasedPermissionManager.hasPermission(WorkflowBasedPermissionManager.java:83)
      7. com.atlassian.jira.security.DefaultPermissionManager.hasPermission(DefaultPermissionManager.java:103)
      8. com.atlassian.jira.security.WorkflowBasedPermissionManager.hasPermission(WorkflowBasedPermissionManager.java:76)
      9. com.atlassian.jira.security.ApplicationRequiredPermissionManager.lambda$hasPermission$235(ApplicationRequiredPermissionManager.java:71)
      9 frames