-
Suggestion
-
Resolution: Duplicate
-
None
-
None
Currently I have to enter the ID of the Sprint (which is not shown anywhere) so that I can create a bug ticket (for example) and assign it to a Sprint using the "Create" screen.
There should be a drop-down for Sprints to choose from not an ID... that is more than inconvenient
- duplicates
-
- Closed
- incorporates
-
- Closed
- is related to
-
- Closed
- relates to
-
- Closed
[JSWCLOUD-9025] As User I want to create an issue and assign it promtly to a Sprint
John Crim
added a comment - The "Sprint drop-down field" portion is covered by GHS-9812 . 
James Rickards
added a comment - 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:
- PM gets e-mail due to being assigned the issue, or due to a mention in a comment...
- PM opens the ticket from the e-mail
- 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.
I have suggested that this function is added under the 'Agile' section, near the 'view on board' button.
I don't really care if it is a popup that forces you to select the board, and then the sprint, or if it is a drop down such as fixVersion.
Either way it needs to be as easy to use as fixVersion.
Regards
James Rickards
added a comment - 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:
PM gets e-mail due to being assigned the issue, or due to a mention in a comment...
PM opens the ticket from the e-mail
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.
I have suggested that this function is added under the 'Agile' section, near the 'view on board' button.
I don't really care if it is a popup that forces you to select the board, and then the sprint, or if it is a drop down such as fixVersion.
Either way it needs to be as easy to use as fixVersion.
Regards 
Oliver Fajardo
added a comment - Agreed. This is a major impediment in our effort to upgrade to the latest Jira/GH. Currently, the Sprint field is numeric. So even if I rename the sprint label, I still have to find out what the actual numeric sprint id is. Ideally, the sprint drop down should show current active sprint, new/inactive sprints, and closed sprints. Further, managing sprint ids should be an option in the Administration section. Thoughts?
Oliver Fajardo
added a comment - Agreed. This is a major impediment in our effort to upgrade to the latest Jira/GH. Currently, the Sprint field is numeric. So even if I rename the sprint label, I still have to find out what the actual numeric sprint id is. Ideally, the sprint drop down should show current active sprint, new/inactive sprints, and closed sprints. Further, managing sprint ids should be an option in the Administration section. Thoughts? 
We are pleased to announce that this issue has now been resolved in JIRA Agile version 6.3.9 which is now available to download.
https://confluence.atlassian.com/display/AGILE/JIRA+Agile+6.3.9+Release+Notes
Thank-you for your feedback and votes on this issue.
Kind regards
Martin
JIRA Agile team