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.

Good news! As of JIRA Agile 6.3.9 this is now possible. The control for editing a sprint on the standard JIRA View/Edit Issue screens allows you to pick any active or future sprint.

Regards,
JIRA Agile Team

+1 from me.
I am facing an issue where we get resistance from PM's for adopting rapid board.
They are used to the ease of using 'fixVersions' to prioritize and manage a set of tickets.
A feature that offers the same ease of use, but with Sprints is desired.

For our product we have over 1000 + tickets on our backlog, and 20-30 unstarted sprints for various programs of work.
In addition we use con-current sprints on a single rapid board. This is all to ensure a single and consistent landing page for staff to work from.

Whilst the planning board is great for planning, and the work board is great for standups, the current system does not support quickly scheduling work directly from the issue.
A typical use case is:

1. PM gets e-mail due to being assigned the issue, or due to a mention in a comment...
2. PM opens the ticket from the e-mail
3. PM wants to schedule the ticket, so usually just sets the fix version, and later goes through all issues in that fix version during scoping/planning meetings
   With green hopper the user has to trawl through a massive backlog and drag the ticket through umpteen un-organised sprints.

Agreed that it's possible with a link, though I'm not sure we'll implement this imminently. Just wanted to point out that we couldn't straight offer a list of existing sprints, we'd need to have one dialog to select a board, then another to select the sprint, it's probably just faster to click 'View on Board', send to top with 's' and 't' then drag the issue in to the sprint.

Thanks,
Shaun

You already do this same work with the "View On Board" button, so I don't understand what the difference is here. The control could be a pop-up dialog so no work would be done unless the user activated the "Send To Sprint" feature.

Hi Greg,

We're unlikely to do this because it's computationally intensive to calculate all of the boards an issue appears on. This is why we don't show the boards by name in the Agile panel at the moment.

Thanks,
Shaun