Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-76621

Error in basic search using Epic Link with closed Epic (uneditable)

    XMLWordPrintable

Details

    • Bug
    • Resolution: Unresolved
    • Low
    • None
    • 9.4.7
    • Issue - Fields
    • None

    Description

      Issue Summary

      Doing a search in basic mode using the Epic Link field, we get the following error: "You don't have permission to edit this epic, so you can't assign your issue to it"

      Doing the same search in advance mode works without any error message being displayed. Even if I select a closed epic.

      Steps to Reproduce

      How to reproduce:
      1- Login as user who is not allowed to edit closed Epic
      2- Create the first Epic named: Basic search x.x
      3- Create a story setting the Epic link field to the first Epic
      4- Resolve the first Epic and then close it
      5- Create a second Epic named: Basic search y.y
      6- Create a story setting the Epic link field to the second epic
      7- Search in basic mode click on more, Epic Link
      8- Start typing a Basic search in the window
      9- Select the closed epic (x.x) and click on update
      10- You should see the error at the bottom


      11- Select the open epic (y.y) and click on update
      12- The search is completed successfully
      13- Click on Advance
      14- Enter the following search: "Epic Link" = "
      15- Start typing: Basic search
      16- Select the closed epic
      17- The search is completed successfully

      Expected Results

      The Basic Search should bring the results according to the parameters set

      Actual Results

      The user receives the error message "You don't have permission to edit this epic, so you can't assign your issue to it"

      Workaround

      • Switch to Advanced Search instead of the Basic Search. There is no validation error when running the JQL search using the Epic Link field.
      • Consider removing the jira.issue.editable workflow property if you are using it. As an alternative, you can also define the workflow property jira.permission.edit.group.1 = jira-user-group-one on Done status for example so the issue is not editable by everybody but only a certain group of users, thus reducing the friction by the users. In turn, however, the users will be able to edit the epic.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              d7087ee2dbf9 Marcos Vinicius
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated: