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

As a scrum user I would like to be able to assign an issue to a sprint from the standard JIRA view issue page

    • Icon: Suggestion Suggestion
    • Resolution: Duplicate
    • None
    • None
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      While viewing an issue via the standard JIRA page I would like a control next to "View on Rapid Board" that allows me to send the issue to any sprint that has not yet been completed on any Rapid Board on which the issue currently appears.

      While allowing issues to be assigned to sprints that have already started in addition to sprints that have not yet started is not good scrum practice, it happens in reality and the control should not restrict the user from doing so, (though it could be useful to indicate that the sprint is already in progress.)

          Form Name

            [JSWSERVER-6019] As a scrum user I would like to be able to assign an issue to a sprint from the standard JIRA view issue page

            I am finding that this feature is still not as convenient as it was intended to be.  On the regular view of issues, even when the Sprint field is included in the issue screen configuration, the field will be hidden because it has no value.  In order for me to edit the Sprint field, the issue must already be in a sprint, and I have to go elsewhere to achieve that.

            Joel Cairney added a comment - I am finding that this feature is still not as convenient as it was intended to be.  On the regular view of issues, even when the Sprint field is included in the issue screen configuration, the field will be hidden because it has no value.  In order for me to edit the Sprint field, the issue must already be in a sprint, and I have to go elsewhere to achieve that.
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3068421 ] New: JAC Suggestion Workflow 3 [ 3662100 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2624741 ] New: JAC Suggestion Workflow [ 3068421 ]
            Rachel Lin (Inactive) made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2326703 ] New: Confluence Workflow - Public Facing v4 [ 2624741 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 [ 2043512 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2326703 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2031645 ] New: JIRA PM Feature Request Workflow v2 [ 2043512 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 [ 737187 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2031645 ]
            Confluence Escalation Bot (Inactive) made changes -
            Labels New: affects-server
            Martin (Inactive) made changes -
            Workflow Original: GreenHopper Kanban Workflow v2 [ 406741 ] New: JIRA PM Feature Request Workflow v2 [ 737187 ]
            Issue Type Original: Story [ 16 ] New: Suggestion [ 10000 ]
            Priority Original: Minor [ 4 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Michael Tokar made changes -
            Resolution New: Duplicate [ 3 ]
            Status Original: Open [ 1 ] New: Resolved [ 5 ]

              Unassigned Unassigned
              3f85ab128771 G B
              Votes:
              10 Vote for this issue
              Watchers:
              10 Start watching this issue

                Created:
                Updated:
                Resolved: