Users with Permission Unable to Move Issues from Resolved to Closed
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
Summary
Users with correct permission are unable to move Issues from Resolved to Closed facing the Unknown error below:
Diagnosis
Using Advanced Roadmaps 3.29.5 and below;
The Team custom field available in the Close Issue Screen;
The Team custom field has a value associated with it;
Workflow with the jira.permission.edit.group property key - How to limit editing permission, to certain groups, for a particular Issue Status;
The user who is trying to make the transition does not belong to the group referenced by the jira.permission.edit.group property key;
The following error appears in the
atlassian-jira.log:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
2021-05-19 12:25:01,054-0300 http-nio-48111-exec-15 INFO USER 745x2405x1 1pe921e 0:0:0:0:0:0:0:1 /secure/CommentAssignIssue.jspa [c.a.jira.security.WorkflowBasedPermissionManager] EDIT_ISSUES not granted by workflow perm granting EDIT_ISSUES to Group 'jira-administrators'
2021-05-19 12:25:01,055-0300 http-nio-48111-exec-15 INFO USER 745x2405x1 1pe921e 0:0:0:0:0:0:0:1 /secure/CommentAssignIssue.jspa [c.a.jira.security.WorkflowBasedPermissionManager] EDIT_ISSUES granted by permission scheme but DENIED by workflow
2021-05-19 12:25:01,055-0300 http-nio-48111-exec-15 ERROR USER 745x2405x1 1pe921e 0:0:0:0:0:0:0:1 /secure/CommentAssignIssue.jspa [c.a.jira.workflow.OSWorkflowManager] Caught exception while attempting to perform action 701 from workflow 10225 on issue 'AR-3'
java.lang.IllegalArgumentException
at com.google.common.base.Preconditions.checkArgument(Preconditions.java:127)
at com.atlassian.jira.entity.property.BaseEntityPropertyService.setProperty(BaseEntityPropertyService.java:96)
at com.atlassian.jira.entity.property.DelegatingEntityPropertyService.setProperty(DelegatingEntityPropertyService.java:41)
at sun.reflect.GeneratedMethodAccessor1566.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.atlassian.plugin.util.ContextClassLoaderSettingInvocationHandler.invoke(ContextClassLoaderSettingInvocationHandler.java:26)
at com.sun.proxy.$Proxy496.setProperty(Unknown Source)
... 2 filtered
at java.lang.reflect.Method.invoke(Method.java:498)
at com.atlassian.plugin.osgi.bridge.external.HostComponentFactoryBean$DynamicServiceInvocationHandler.invoke(HostComponentFactoryBean.java:131)
at com.sun.proxy.$Proxy496.setProperty(Unknown Source)
at com.atlassian.rm.common.bridges.jira.issue.properties.IssuePropertyServiceBridge81.setProperty(IssuePropertyServiceBridge81.java:83)
at com.atlassian.rm.common.env.issues.JiraIssuePropertyService.setProperty(JiraIssuePropertyService.java:263)
at com.atlassian.rm.common.env.issues.JiraIssuePropertyService.set(JiraIssuePropertyService.java:104)
at com.atlassian.rm.teams.customfields.team.TeamIssuePropertyService.setTeamId(TeamIssuePropertyService.java:30)
at com.atlassian.rm.teams.customfields.team.IssueTeamService.setTeam(IssueTeamService.java:46)
at com.atlassian.rm.teams.customfields.team.TeamCustomFieldTypeHelper.setTeamOnIssue(TeamCustomFieldTypeHelper.java:105)
at com.atlassian.rm.teams.customfields.team.TeamCustomFieldType.updateValue(TeamCustomFieldType.java:79)
at com.atlassian.rm.teams.customfields.team.TeamCustomFieldType.updateValue(TeamCustomFieldType.java:22)
at com.atlassian.jira.issue.fields.ImmutableCustomField.updateValue(ImmutableCustomField.java:426)
at com.atlassian.jira.issue.fields.ImmutableCustomField.updateValue(ImmutableCustomField.java:396)
at com.atlassian.jira.workflow.function.issue.GenerateChangeHistoryFunction.execute(GenerateChangeHistoryFunction.java:54)
at com.opensymphony.workflow.AbstractWorkflow.executeFunction(AbstractWorkflow.java:1014)
at com.opensymphony.workflow.AbstractWorkflow.transitionWorkflow(AbstractWorkflow.java:1407)
at com.opensymphony.workflow.AbstractWorkflow.doAction(AbstractWorkflow.java:557)
at com.atlassian.jira.workflow.OSWorkflowManager.doWorkflowActionInsideTxn(OSWorkflowManager.java:842)
at com.atlassian.jira.workflow.OSWorkflowManager.doWorkflowAction(OSWorkflowManager.java:799)
at com.atlassian.jira.bc.issue.DefaultIssueService.transition(DefaultIssueService.java:517)
at com.atlassian.jira.web.action.issue.CommentAssignIssue.doExecute(CommentAssignIssue.java:161)
... 1 filtered
at com.atlassian.jira.action.JiraActionSupport.execute(JiraActionSupport.java:63)
... 7 filtered
at javax.servlet.http.HttpServlet.service(HttpServlet.java:741)
... 48 filtered
at com.atlassian.greenhopper.jira.filters.ClassicBoardRouter.doFilter(ClassicBoardRouter.java:56)
... 7 filtered
at com.atlassian.jira.plugin.mobile.web.filter.MobileAppRequestFilter.doFilter(MobileAppRequestFilter.java:59)
... 4 filtered
at com.atlassian.jira.plugin.mobile.login.MobileLoginSuccessFilter.doFilter(MobileLoginSuccessFilter.java:54)
... 3 filtered
at com.atlassian.diagnostics.internal.platform.monitor.http.HttpRequestMonitoringFilter.doFilter(HttpRequestMonitoringFilter.java:55)
... 8 filtered
at com.atlassian.web.servlet.plugin.request.RedirectInterceptingFilter.doFilter(RedirectInterceptingFilter.java:21)
... 62 filtered
at com.atlassian.jira.security.JiraSecurityFilter.lambda$doFilter$0(JiraSecurityFilter.java:66)
... 1 filtered
at com.atlassian.jira.security.JiraSecurityFilter.doFilter(JiraSecurityFilter.java:64)
... 39 filtered
at com.atlassian.jira.servermetrics.CorrelationIdPopulatorFilter.doFilter(CorrelationIdPopulatorFilter.java:30)
... 10 filtered
at com.atlassian.web.servlet.plugin.request.RedirectInterceptingFilter.doFilter(RedirectInterceptingFilter.java:21)
... 4 filtered
at com.atlassian.web.servlet.plugin.LocationCleanerFilter.doFilter(LocationCleanerFilter.java:36)
... 29 filtered
at com.atlassian.jira.servermetrics.MetricsCollectorFilter.doFilter(MetricsCollectorFilter.java:25)
... 25 filtered
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Thread.java:748)Cause
When adding the jira.permission.edit.group property to the workflow we will limit the ability to edit to a certain group after the issue is closed, as described in the following documentation:
How to limit editing permission, to certain groups, for a particular Issue Status
Therefore, if any user outside this group tries to move the issue from Resolved to Closed, Jira will present an error during this transition, as the Advanced Roadmaps Team field tries to update the issue that cannot be edited. This is addressed in the following bug ticket:
Solution
Upgrade to Advanced Roadmaps 3.29.6+, since this bug has been fixed in higher versions.
Was this helpful?