Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-8966

Scrum Board throwing Error when moving issue into Sprint without the Schedule Issue Permission

      Steps to Reproduce

      • Ensure that you don't have the Schedule Issue permission
      • Sprint 1 is showing the issues as follows (TESTONE-1 until TESTONE-5). Backlog has TESTONE-7 until TESTONE-10
      • When moving TESTONE-8 into the sprint, the following Error message appears. TESTONE-8 is no longer in the Backlog but the Sprint does not refresh to contain the issue
      • However, the issue is present when you move to the Work Mode of the Board
      • Or when you refresh the page after an issue is added to the Sprint

        1. schedule_permission.JPG
          schedule_permission.JPG
          33 kB
        2. scrum_1.JPG
          scrum_1.JPG
          131 kB
        3. scrum_2.JPG
          scrum_2.JPG
          144 kB
        4. scrum_3.JPG
          scrum_3.JPG
          106 kB
        5. scrum_4.JPG
          scrum_4.JPG
          146 kB

          Form Name

            [JSWSERVER-8966] Scrum Board throwing Error when moving issue into Sprint without the Schedule Issue Permission

            Unable to reproduce this bug anymore with the latest version of JIRA and JIRA Agile. Hence closing it.

            Kiran (Inactive) added a comment - Unable to reproduce this bug anymore with the latest version of JIRA and JIRA Agile. Hence closing it.

            I agree that this should be higher priority. Developers should know better than to add issues from the backlog but I want Jira Agile to prevent the possibility. Please consider raising the priority.

            Mark Eskandar added a comment - I agree that this should be higher priority. Developers should know better than to add issues from the backlog but I want Jira Agile to prevent the possibility. Please consider raising the priority.

            This should have higher priority. Companies are required to have this type of securities in place by standards organizations.

            Nimitt Desai added a comment - This should have higher priority. Companies are required to have this type of securities in place by standards organizations.

            It's affect us because we have a lot of sprints created in past and need ensure that nobody can assign issue to sprint if has not permission 'schedule'.

            Eleveo Admin added a comment - It's affect us because we have a lot of sprints created in past and need ensure that nobody can assign issue to sprint if has not permission 'schedule'.

              Unassigned Unassigned
              adanial Ahmad Danial (Inactive)
              Affected customers:
              4 This affects my team
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: