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

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

            Bugfix Automation Bot made changes -
            Minimum Version New: 6.02
            Owen made changes -
            Workflow Original: JAC Bug Workflow v2 [ 2850751 ] New: JAC Bug Workflow v3 [ 2933819 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v7 - Restricted [ 2545411 ] New: JAC Bug Workflow v2 [ 2850751 ]
            Ignat (Inactive) made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - Restricted [ 1549342 ] New: JIRA Bug Workflow w Kanban v7 - Restricted [ 2545411 ]
            jonah (Inactive) made changes -
            Description Original: # A board is defined for a project X.
            # A sprint is created and an issue in project X is added to it from the backlog.
            # 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.
            # 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
            # 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
            		New: {panel:bgColor=#e7f4fa}
              *NOTE:* This bug report is for *JIRA Software Server*. Using *JIRA Software Cloud*? [See the corresponding bug report|http://jira.atlassian.com/browse/JSWCLOUD-9499].
              {panel}

            # A board is defined for a project X.
            # A sprint is created and an issue in project X is added to it from the backlog.
            # 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.
            # 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
            # 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
            jonah (Inactive) made changes -
            Link New: This issue relates to JSWCLOUD-9499 [ JSWCLOUD-9499 ]
            Confluence Escalation Bot (Inactive) made changes -
            Labels Original: affects-server fixme New: affects-cloud affects-server fixme
            Confluence Escalation Bot (Inactive) made changes -
            Labels Original: fixme New: affects-server fixme
            Owen made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 909151 ] New: JIRA Bug Workflow w Kanban v6 - Restricted [ 1549342 ]
            Oswaldo Hernandez (Inactive) made changes -
            Workflow Original: GreenHopper Kanban Workflow 20141014 [ 747473 ] New: JIRA Bug Workflow w Kanban v6 [ 909151 ]

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

                Created:
                Updated:
                Resolved: