IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.

      Issue Summary

      Users lacking the 'Edit Issues' permission are not able to link an Epic to newly created or existing issues. However, despite an error message when performing this action, a new issue is still created and the workflow is left in a broken state for that issue.

      This issue was introduced in JSW 8.11.0 and is not occurring in 8.10.1.

      Steps to Reproduce

      1. Create two Software projects.
      2. Remove 'Edit Issues' permission in the Project A permission scheme.
      3. Create an Epic in 'Project A'.
      4. Create a new issue (or edit existing issue) in 'Project B' with the Epic Link assigned to the Epic created in step 3.

      Expected Results

      The issue is not created because the user does not have the appropriate permission. See JSWSERVER-13986 for a related suggestion.

      Jira Software considers linking issues to epics as editing the scope of work of an epic, which is why it uses the "Edit issue" permission to check if a user is able to link/unlink issues to an epic.

      Actual Results

      As of 8.11, the user gets an unclear error message that is shown in the screenshot and the impression the issue isn't submitted:

      We can't create this issue for you right now, it could be due to unsupported content you've entered into one or more of the issue fields. If this situation persists, contact your administrator as they'll be able to access more specific information in the log file.
      

      However:

      1. The issue is created without the Epic Link or required fields.
      2. The os_wfentry.state for the issue is set to 0 so no workflow transition button appears on the view issue screen.
      New Issue

      /secure/QuickCreateIssue.jspa [c.a.j.bc.issue.DefaultIssueService] Error creating issue:
      com.atlassian.jira.exception.CreateException: You do not have permission to edit issue PROJECTA-1.
      

      OS_WFENTRY:

      ID NAME INITIALIZED STATE
      10601 Software Simplified Workflow for Project SCRUM NULL 0
      Existing Issue

      /secure/QuickEditIssue.jspa [c.a.j.bc.issue.DefaultIssueService] Exception occurred editing issue: java.lang.RuntimeException: You do not have permission to edit issue PROJECTA-1.
      java.lang.RuntimeException: You do not have permission to edit issue PROJECTA-1.
      

      Workaround

      The workaround is to:

      1. Search for the new issue – either by direct URL or through the database.
      2. Add the required fields and Epic Link (under a user that has permission).
      3. Fix the workflow with the KB Workflow transition button missing from the issue view page in Jira server.

      Always back up your data before performing any modifications to the database. If possible, test any alter, insert, update, or delete SQL commands on a staging server first.

        1. ExistingIssue.png
          ExistingIssue.png
          11 kB
        2. NewIssue.png
          NewIssue.png
          22 kB

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.

                Issue Summary

                Users lacking the 'Edit Issues' permission are not able to link an Epic to newly created or existing issues. However, despite an error message when performing this action, a new issue is still created and the workflow is left in a broken state for that issue.

                This issue was introduced in JSW 8.11.0 and is not occurring in 8.10.1.

                Steps to Reproduce

                1. Create two Software projects.
                2. Remove 'Edit Issues' permission in the Project A permission scheme.
                3. Create an Epic in 'Project A'.
                4. Create a new issue (or edit existing issue) in 'Project B' with the Epic Link assigned to the Epic created in step 3.

                Expected Results

                The issue is not created because the user does not have the appropriate permission. See JSWSERVER-13986 for a related suggestion.

                Jira Software considers linking issues to epics as editing the scope of work of an epic, which is why it uses the "Edit issue" permission to check if a user is able to link/unlink issues to an epic.

                Actual Results

                As of 8.11, the user gets an unclear error message that is shown in the screenshot and the impression the issue isn't submitted:

                We can't create this issue for you right now, it could be due to unsupported content you've entered into one or more of the issue fields. If this situation persists, contact your administrator as they'll be able to access more specific information in the log file.
                

                However:

                1. The issue is created without the Epic Link or required fields.
                2. The os_wfentry.state for the issue is set to 0 so no workflow transition button appears on the view issue screen.
                New Issue

                /secure/QuickCreateIssue.jspa [c.a.j.bc.issue.DefaultIssueService] Error creating issue:
                com.atlassian.jira.exception.CreateException: You do not have permission to edit issue PROJECTA-1.
                

                OS_WFENTRY:

                ID NAME INITIALIZED STATE
                10601 Software Simplified Workflow for Project SCRUM NULL 0
                Existing Issue

                /secure/QuickEditIssue.jspa [c.a.j.bc.issue.DefaultIssueService] Exception occurred editing issue: java.lang.RuntimeException: You do not have permission to edit issue PROJECTA-1.
                java.lang.RuntimeException: You do not have permission to edit issue PROJECTA-1.
                

                Workaround

                The workaround is to:

                1. Search for the new issue – either by direct URL or through the database.
                2. Add the required fields and Epic Link (under a user that has permission).
                3. Fix the workflow with the KB Workflow transition button missing from the issue view page in Jira server.

                Always back up your data before performing any modifications to the database. If possible, test any alter, insert, update, or delete SQL commands on a staging server first.

                  1. ExistingIssue.png
                    ExistingIssue.png
                    11 kB
                  2. NewIssue.png
                    NewIssue.png
                    22 kB

                        drauf Daniel Rauf
                        43408485a508 Nathan Lopez
                        Votes:
                        11 Vote for this issue
                        Watchers:
                        28 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                            drauf Daniel Rauf
                            43408485a508 Nathan Lopez
                            Affected customers:
                            11 This affects my team
                            Watchers:
                            28 Start watching this issue

                              Created:
                              Updated:
                              Resolved: