-
Suggestion
-
Resolution: Unresolved
-
None
-
204
-
16
-
On June 21 2021, an update was released to resolve JRACLOUD-40929 (which was opened 18 November 2014). That update which adds some sort options does not resolve the issue.
The point is for the user to choose which issue is #1, which is #2, which is #3 all the way to the last issue not to sort according to a few pre-defined options. This could be achieved by for example allowing issues to be dragged up and down to reorder them.
- is related to
-
- Gathering Interest
[JRACLOUD-76877] Move issues up and down in Epic to any desired position (manual re-order rather than sort)
c3921c8fb0cc it looks like Jira Plans is available only for Jira Premium and Enterprise.
This feature, JRACLOUD-76877, is so basic that it should be available to all users regardless of what type of Jira subscription they are using.
The only way i've been able to handle this is by using plans. You can sort things using plans and push those changes back to Jira.
2239430e27fb is this feature available for company managed project?
If yes, please let us know how to activate it.
Also not available for me, hopefully it will become generally available at some point...
a85f6c7dbb13 I have also tested and do not have the drag/drop indicator you have in your video.
I tried everything I could to replicate your video. 3 browsers, dark/light mode, shrinking the width to match yours, many a refresh and cash clears... nothing ever shows up for the drag/drop indicator. Your video looks terrific, exactly what we need. Maybe your part of some prerelease group? I did have a chat with atlassian, was contacted for a survey... this ticket was discussed a great deal.
18c7a2422d3b I am looking directly at the Epic ticket. Could you please take a look at this video? Are you doing something different than what I am doing?
a85f6c7dbb13 I assume your looking at some board, not an actual EPIC ticket. As far as local, can only do it in timeline view which no one uses in my company. One can drag and drop subtasks in a story with a ticket open, but not stories in an epic. Both control the same Rank variable, or should. This is critical, because when someone works a ticket, they aren't looking at the timeline they are looking at the ticket... same for the 20 departments we have managing epics, its a disaster, every single project, tasks are worked in random order.
This seems complete. While viewing an epic, I'm able to drag and drop issues to reorder them.
You and several of your fellow commenters can also use the Feedback for the Founders link at https://www.atlassian.com/company/contact/contact-ceos. Reference the JIRA, how many folks that are wanting it, why this is causing problems for you, and if any competitors already have the functionality.
@alex - that's nuts... dark mode is number 1... if you don't build an app this large to be themable from the onset, that ends up being a 3 year project. I hope your wrong, they aren't prioritizing by user 'wants' alone.
For those constantly commenting about 'escalating' and such things, please see the issues ordered by number of votes [here|https://jira.atlassian.com/projects/JRACLOUD/issues/JRACLOUD-63150?filter=allissues&orderby=votes+DESC%2C+priority+DESC%2C+updated+DESC.]
I'm not from Atlassian but I suspect other issues with more votes will be prioritised before this. If you want this to be worked on sooner, more people will probably need to vote for it.
How do we escalate this to the Jira development team? This issue has been reported 2 and half years ago 
ATTENTION ALL: If you have a support contract, open a ticket. They aren't reviewing these obviously... they have no control over their software... why are we still using Jira when 2 years is the best response time Atlassian can achieve with it, beats me.
HIGH PRIORITY - Ability to manually reorder Stories within an Epic OR subtasks within a Story
This is impeding work we do on a daily basis. As a Scrum Master and team member, we want the work to be prioritized so that we can manage prerequisites and dependencies within the issue. This is a DAILY need for us.
Problem: I used to have the ability to reorder stories within an epic…or subtasks within a Story.
This is needed because we want this listed in order so we can fix them in order. The ability to sort by key, priority, etc, is not sufficient.
Desire:
1. Ability to Drag and Drop to reorder.
2. Ability to move up and move down isn’t ideal when you have 10+ items and need to change up the order. Drag and drop or an ability to specify the row position is the optimal way.
This is getting strong votes and emotions for what seems rather simple. This has been logged for 2.5 +years.
Is there a plan to implement this and if so, when?
They aren't listening. They probably aren't aware... this company clearly has a monstrous agile design process... where a ticket can exist for 3 years with out a reply. Where the original ticket this one is based off of was implemented incompetently and made the situation worse by way of pointless features. I can't imagine why anyone would actually want to use this software at this point... at least not the dam near 5,000 that vote for this thread or similar ones over the last decade. The worst part, the have it for subtasks, so frontend wise this should be a 1 pointer, backend max 1 extra field... in crazy Jira terminology that's like 3 story points... in normal human engineer speak, not a fairytail character in a choose your own adventure story, 40 man hours max. w/ tests... if it where me, I'd make sure this exists on all child issue displays (for each ticket type) in that time, might as well do it for linked issues as well... different people use Jira differently within the same company, rarely is there any training on work/project management.... "that's not agile" Jira would say... I would say agile is as bad as waterfall, neither exists in the real world... both completely describable by 3 block flow chart... managing real projects is not so black and white, agile/waterfall are extremes, they tell you only the bounds... Jira is built with both, but the programmers don't seem to realize it.
Way to set an example Atlassian!
This is badly needed because the current sorting options on the Epic are insufficient.
We want to hand-sort the stories on the Epic to their natural order.
HIGH PRIORITY - Ability to manually reorder Stories within an Epic OR subtasks within a Story
This is impeding work we do on a daily basis. As a Scrum Master and team member, we want the work to be prioritized so that we can manage prerequisites and dependencies within the issue. This is a DAILY need for us.
Problem: I used to have the ability to reorder stories within an epic…or subtasks within a Story.
This is needed because we want this listed in order so we can fix them in order. The ability to sort by key, priority, etc, is not sufficient.
Desire:
1. Ability to Drag and Drop to reorder.
2. Ability to move up and move down isn’t ideal when you have 10 items and need to change up the order. Drag and drop or an ability to specify the row position is the optimal way.
This feature should not be too complicated to implement, because reordering of lists by drag & drop is already available in Jira almost everywhere else. Thus, no wheel reinvention needed. It's actually more like a surprise to the Jira user that tickets in Epics cannot be reordered at all.
FYI community, I have a workaround for it.
Go in PLAN, find your epic, reorder the stories there.
Update your plan.
Your stories are now in the right order the EPIC
Man, you know the worst part... they don't even have sort by title... if they had that at least we would have a workaround, something that would also encourage consistent ticket names, inherently sortable ticket titles.
Agreed. Sorts are virtually useless here, sorts of this nature are used for research and planning, not the ticket implementer/user... top down list, what to work in the correct order... everyone needs that to be competent at there job... even working at McDonalds, there is a sequence of events to constructing a hamburger... one only cares about the correct sequence, not the sequences of priority, key, created by, status... or assignee. Even if these sequences were right for any particular ticket in any particular stage, they don't save so all the sorted 'assignees' (for whatever reason) have no idea which is right, and everything is worked in the wrong sequence, effectively randomly... Atlassian has claimed this is the AGILE way and that's the reason they refuse to implement a Manual sort feature for epics, while they already implemented it for stories... sounds like an excuse to me... Every ticket is inefficiently worked because of this, meaning the code isn't evolving naturally and we are being left with frankenstein results...2 pieces of lettuce, wrapped around a hamburger, with ketchup on top.
Ultimately, pretty darn furious Atlassian isn't addressing this issue causing so much inefficient work across world... but it's become what I expect from them.
So with the recent change to backlog view making it slightly more difficult to scan and filter by epic I think this is now even more important.
I'm fine with losing the other sort options just to be able to get this functionality, or disable the drag'n drop control if the sort is anything other than rank.
This is possible, and important for us.
The worst part is the implemented it correctly for subtasks on a story, so hundreds of people are are creating massive 100 point stories just to be able to sequence tasks... something I could do with a spreadsheet in 1989, this software can't do. What else is there to say, the justifications I've heard from them are nonsense.
the approach https://jira.atlassian.com/browse/JRACLOUD-40929 feels like an intentional slap in the face for what was actually requested.
to be clear, i want user-determined, manual drag & drop for items within an epic that persists independently of the items completion status, appearance in a sprint, etc.
thank you
Seriously low hanging fruit for you guys that seriously affects our companies bottom line. We get thousands of feature requests and bug reports for hundreds of applications. Epics allow us to group things so our limited dev staff isn't forced to jump around continuously and reacclimate to new programs literally every day for every task; i.e. the overall agile goal or project. Stories on the epics allow us to get things done in a sprint, discrete deliverables, the pieces of an agile sprint. Subtasks, spikes and everything else we are starting to only allow on the stories, not the epics, as it is significant;y more efficient to manage, naturally hierarchical, and in the end all this precursor work tends to be part of the story in reality anyway... often tasks are more planning than implementing, at least if your practicing real fundamental engineering.
Hence, we have the concept of a root ticket, usually an EPIC but we work stories. Now the problem. When users and managers are in the stories, they can drag and drop the subtasks; it's become a method of communication across the team, a super intuitive one... top down is always the ideal order to work the subtasks for efficiency. For example, backend, frontend.... if we work frontend, backend, then we almost always always need an integration stage and the overhead of the acclimating, PR reviews, testing, UAT, release, each isn't really justifiable. Great, we have an absolutely necessary feature in stories, sequencability of subtasks and related. But for epics, the root ticket needed to be worked over MANY sprints, were we REALLY need that sequencing control on a per project basis, we don't have it.
We often have to move the content and title from one ticket to another, so we've been planning our epics outside Jira to avoid that... which shows the serious flaw in the software.
What would it take to fix? 3 story points... the problem is your replicating code, not standardizing the same structures, and generally not providing great service because... well, probably the same reason we are in that boat... the tool you are using is not up to the task of coordinating 100s of people in a less than reactionary way.
Please allow this simple fix, for the love of god please!
Please add this functionality, it would make managing projects so much easier!
This feature is done!
Now spin the wheel to see who
Will get to use it.
I'd be insanely curious for the explanation behind why this feature is already implemented in team-managed projects but not company-managed ones, because it makes negative sense to me.
Please add this functionality, it would make managing child issues so much easier when we walk the board!
This is like the most basic feature in a project management tool to visual dependencies, track progress and prioritize tickets. It's mind boggling that Jira doesn't support this. Wow!
Hi Atlassian, I want a sort option on the statuses of the issues in an epic.
This is 2023! What's it going to take to implement this feature? I think the only reason there aren't more votes is people don't realize they can vote on the issue until they are frustrated by the Rank to Top/Rank to Bottom that they go searching for a solution.
+1
I don't think this was mentioned previously... In the "Issues in Epics" section of an Epic, when you select a different sort method (by sprint, status, whatever...) it would be helpful if that selection would "stick" so that the next time you view the Epic, you don't have to select it again. Thanks!
Our users need possibility to rank children in epics, in the same way as in board.
Board ranking is still needed on the board level.
So 2 levels of ranking are needed.