Dear team,
I am curious if possible to use Drag&Drop prioritization (using Rank) possible on the Dashboard and with Saved Filter.
For example, I can move items saved as filter but when the search is refreshed, items return back to original order. I just found that Ordering by Rank ASC is a requirement for the drag&drop to work so my search is like that.
Thanks for for you comment, feedback.
Frank
Hi @Frantisek Kust,
As far as I know, reordering items can be done on a scrum or kanban board (both in backlog or active sprint/issue views). Changing the order of items updates the underlying rank of the issues in the database, so the reordering persists.
Although you can reorder items in your filter results on screen, this does not update the underlying rank. Which is the reason why refreshing restores the previous order.
So in short: if you want to reorder using drag and drop, you can. But do it on a scrum or kanban board if you want your changes to persist.
Thanks, Walter. I thought that is exactly as you described, just I wasn't sure if I am not missing any setting there!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
How does one reorder the issues via drag and drop in a filter view? I don't see a place to grab the issue for dragging ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Same, really want this as a planning functionality within jira's filter feature.
Now, I open a doc in confluence, copy/paste issue URLs. when the integrated pills load, I then copy/paste the pills to change the order (drag/drop is not possible) in the raw doc in order to more clearly plan dependencies within epics before a sprint's start.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It's really kind of critical for being able to establish a FLOW of working. Whether you are working through code doing fixes, or testing bug fixes/test cases (my situation), you need to be able to organize tickets in such a way that the workflow is natural to the functionality of what you are testing. Attempting to create that order via database using a datafield is more than cumbersome.
Without the ability to manually order your ticket queue, in a view that you can actually use to work through the bug tickets without drilling into each one, you're doomed to having to re-cover ground because ticket 426 also covers an area that ticket 4 did, which you've already tested. So... you have to test that area again.
Atlassian.... please please please give us this functionality :-)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, my QA team would die for drag and drop functionality in save filters. The whole point is to be able to manually order jira items that appear in a saved filter's results, and save the manually arranged order, without a key-driven (field-driven) dependency programmed into the filter.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.