-
Bug
-
Resolution: Duplicate
-
Low
-
None
-
8.13.3, 8.15.0
-
None
-
8.13
-
1
-
Severity 3 - Minor
-
Issue Summary
Adding an epic in the epic link field for which the user doesn't have "edit issue" permission results in an error
Steps to Reproduce
- Create 2 projects with 2 different permission schemes(say Project A & Project B)
- now in the permission scheme restrict the "edit issues" permission for a few users/groups on Project B.
- Create an issue of type "Epic" and mark it as done in Project B
- Try to create an issue in Project A as a user who doesn't "edit issues" permission in Project B.
- in the epic link field try to select the Epic that was created in the project B and click on "create" button
Expected Results
the issue should be created without any errors or warnings.
Actual Results
the below exception appears in the atlassian-jira.log
2021-03-29 16:03:22,694+0530 http-nio-48133-exec-21 ERROR testuser 963x2284x1 ydhntm 0:0:0:0:0:0:0:1 /secure/QuickCreateIssue.jspa [c.a.j.bc.issue.DefaultIssueService] Error creating issue: com.atlassian.jira.exception.CreateException: You do not have permission to edit the following issues: PB-1, PROJ-1. at com.atlassian.jira.issue.managers.DefaultIssueManager.createIssue(DefaultIssueManager.java:600) at com.atlassian.jira.issue.managers.DefaultIssueManager.createIssue(DefaultIssueManager.java:501) at com.atlassian.jira.issue.managers.RequestCachingIssueManager.createIssue(RequestCachingIssueManager.java:195) at com.atlassian.jira.bc.issue.DefaultIssueService.create(DefaultIssueService.java:256) at com.atlassian.jira.bc.issue.DefaultIssueService.create(DefaultIssueService.java:224) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at com.atlassian.plugin.util.ContextClassLoaderSettingInvocationHandler.invoke(ContextClassLoaderSettingInvocationHandler.java:26) at com.sun.proxy.$Proxy318.create(Unknown Source) at java.base/jdk.int
and an error as mentioned in the screenshot.
It was observed that these issues are being created however not being searching using JQL
Workaround
- run the database integrity checker.
- and then run a full reindex
- This will make the issues searchable.
- is resolved by
-
-
- Closed
-