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

Moving issues can stop a sprint from being completed

XMLWordPrintable

      NOTE: This bug report is for JIRA Software Server. Using JIRA Software Cloud? See the corresponding bug report.

      1. A board is defined for a project X.
      2. A sprint is created and an issue in project X is added to it from the backlog.
      3. The same issue is now moved to a different project Y and so it no longer appears on the board but the Sprint field is still set for the issue.
      4. A User with project admin permission for project X but not project Y tries to close the sprint. GreenHopper says that the moved issue in project Y is stopping the sprint from being completed because the user doesn't have project admin permission
      5. If the user cannot edit the Sprint field directly there is no easy way to complete their sprint except to move the issue from Y back to X, view it in GreenHopper and use Remove from Sprint there, then move it back to Y

          Form Name

            [JSWSERVER-9499] Moving issues can stop a sprint from being completed

            Michael Tokar added a comment -

            This issue is actually a duplicate of GHS-6850. Please follow that issue for updates.

            Regards,
            JIRA Agile team

            Michael Tokar added a comment - This issue is actually a duplicate of GHS-6850 . Please follow that issue for updates. Regards, JIRA Agile team

            MichaelA (Inactive) added a comment -

            Since JAG 6.3.9 it is now easier to edit the sprint field.

            https://confluence.atlassian.com/display/AGILE/JIRA+Agile+6.3.9+Release+Notes

            MichaelA (Inactive) added a comment - Since JAG 6.3.9 it is now easier to edit the sprint field. https://confluence.atlassian.com/display/AGILE/JIRA+Agile+6.3.9+Release+Notes

            Gal Gavish added a comment -

            Any idea when this will be fixed? It's happening on a regular basis and causing serious delays in closing sprints and moving forward.
            Thanks!

            Gal Gavish added a comment - Any idea when this will be fixed? It's happening on a regular basis and causing serious delays in closing sprints and moving forward. Thanks!

            Michael Tokar added a comment -

            matt.doar,

            Can the Sprint field now be edited directly in JIRA in Agile 6.3?

            The sprint field can be edited (this has been possible for some time). However the input control is just a basic text field, which expects the IDs of sprints in a comma-separated list. So it's not very useable at this stage.

            Michael Tokar added a comment - matt.doar , Can the Sprint field now be edited directly in JIRA in Agile 6.3? The sprint field can be edited (this has been possible for some time). However the input control is just a basic text field, which expects the IDs of sprints in a comma-separated list. So it's not very useable at this stage.

            MattS added a comment -

            Can the Sprint field now be edited directly in JIRA in Agile 6.3?

            MattS added a comment - Can the Sprint field now be edited directly in JIRA in Agile 6.3?

              Unassigned Unassigned
              73d805a2526b MattS
              Affected customers:
              8 This affects my team
              Watchers:
              16 Start watching this issue

                Created:
                Updated:
                Resolved: