-
Suggestion
-
Resolution: Fixed
-
None
-
13
-
13
-
-
Original summary Ability to use right-click "Add to Sprint" for issues in a backlog sorted by something other than rank
Although it is currently possible to change the filter on a rapid board to show the backlog sorted by something other than "Rank", doing so completely locks the backlog so that you can't change the order OR move backlog issues into the current sprint.
I understand completely why the backlog ranking is locked in this case and am not asking you to change this behaviour.
What I do want is to be able to Right-Click on an issue in the backlog and "Send to Current Sprint".when the board is sorted by anything other than rank.
This would allow me to view and assign issues to the sprint during sprint planning while using a view that is based on my idea of priority (i.e. business value), but would not require any changes to the default rank mechanic.
This simple change would save me hours! Dragging and dropping issues to sort them in a list of several hundred items is just not workable.
- is duplicated by
-
- Closed
-
- Closed
-
- Closed
-
- Closed
- is related to
-
- Closed
-
- Closed
- relates to
-
- Gathering Interest
-
RUM-2434 Loading...
-
- mentioned in
-
-
-
-
-
-
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSWSERVER-11763] Ability to use sprints when backlog not sorted by rank
| Workflow | Original: JAC Suggestion Workflow [ 3070605 ] | New: JAC Suggestion Workflow 3 [ 3663555 ] |
| Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Did this change the way items are sorted in epics in teh back end? I had a script i was using that was fetching issues in an epic and then iterating through them. The order was based on rank but not it seems to be based on key. It's completely broken my script logic. help!
| Current Status |
Original:
{panel:title=Atlassian Status as at March 2017| borderStyle=solid| borderColor=#cccccc| titleBGColor=#dddddd| bgColor=#ffffff}
This feature is now available in JIRA Software Cloud. All boards, including those not ordered by rank, now allow issues to be moved into sprints via drag and drop or using the card context menu, and issues can be dragged to epics or versions for assignment. Kind regards, Martin JIRA Software {panel} |
New:
{panel:title=Atlassian Update – 21 December 2018|borderStyle=solid|borderColor=#ebf2f9|titleBGColor=#ebf2f9|bgColor=#ffffff}
Dear Jira users, We’re glad to announce that this issue will be addressed in our upcoming 8.0 release. You can find more details about our 8.0 beta release here — https://community.developer.atlassian.com/t/beta-for-jira-8-0-is-up-for-grabs/25588 Looking forward to your feedback! Kind regards, Syed Masood Product Manager, Jira Server and Data Center {panel} |
| Workflow | Original: Confluence Workflow - Public Facing v4 [ 2622779 ] | New: JAC Suggestion Workflow [ 3070605 ] |
This is going to version 8.0.0. Unfortunately, I can't tell the exact release date as it's not fixed yet. But I would say that we should not expect it earlier than mid of November.
@snatkovskyi, Could you please provide the approximate release date?
| Fix Version/s | New: 8.0.0 [ 79796 ] | |
| Fix Version/s | Original: 7.13.0 [ 81292 ] |
| Remote Link | New: This issue links to "Page (Confluence)" [ 387881 ] |
Hello rob.a.berube,
depending on how you're fetching issues in an epic, yes, the order might have changed in the back end.
What you could do in your script is to specifically tell Jira to order issues by Rank using JQL query.
For example:
Hope this helps.