This is a feature that will make the use of Kanban board efficient again.  The inability to transit a Jira to the next state in the same column by drag and drop requires much more steps and time to perform such function in an alternative way.  

Appreciate if you can prioritise this Jira to make the Kanban board agile again.

There is a similar issue in JSCloud JSWCLOUD-11639 Dragging issue to other status in same column - Create and track feature requests for Atlassian products.
which unfortunately has been closed. I think its the same and also very important, at least for KANBAN and the pull principle!
I do have the status "in DEV" and "Ready for QA" which are needed to be in one column "in DEV" - but the engineer can't move forward on the board... very uncomfortable... But he needs to move it into "Ready for QA" and the QA has to pull from that column. Otherwise the WIP limits and pull system don't work correctly.

How many more votes does this need for it to be part of the next update??

Any news on when this can be prioritised?

This issue is 10 years old - what would be the problem with providing this functionality - there's a clear use case, with no down side!

The irony is we've settled on a provider of agile development management software who takes decades to consider new features. Not very agile.

Another comment on JSWCLOUD-3573 expressed even better what I mean: https://jira.atlassian.com/browse/JSWCLOUD-3573?focusedCommentId=1499280&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-1499280

With screen space being so precious, especially now when many users are working from home with smaller screens than at work, it would be good to combine two (or more) states in one column in order to support the pulling of issues as workflow.

This is especially important because quick filters can hide issues but don't hide or collapse entire columns when the corresponding state is excluded by the quick filter (understandably, as it might still be a transition target but not solving the screen space issue).

This is a really simple and straight forward feature. Not sure why this wasn't included in out of the box. I would expect to be able to going into either a Sprint or Kanban board's configuration and check a box to allow drag and drop between different statuses in the same column.

This is essential functionality for Kanban.  Please prioritize.

How many years are we going to "Gather Interest" on this topic? Does anyone know of a plugin that already does this we could use?

+1

+1

Just moved a couple of things into the same columns to keep columns from being too skinny and now I'm running into this

This would be a cool thing to have.

PS. Thanks for the workaround: https://www.atlassian.com/blog/archives/jira-tip-of-the-month-dot-and-comma-dialog-shortcuts

+1

is there any update on when this will be picked up?

@Radnor Solutions - Power Boards for Jira looks awesome!  - BUT I am using Jira Cloud.  Are there plans to extend your app to the Jira Cloud platform?

+1

Can't understand why this isn't done yet.. It should not be that big of a deal to implement and it's a big constraint when using kanban.

Hi guys,

I know it's a feature that you want included in Jira but we added this feature to our add-on:

https://marketplace.atlassian.com/apps/1219812/power-boards-for-jira?hosting=server&tab=overview

If you would like to give it a try we would really appreciate any feedback.

Thanks!

+1

I really can't understand why you could do it when coming from another column, but not within the same column...

Would be great to be able to transition issues to statuses within the same column on an agile board. Seems a simple, obvious request.

Really could do with an official Atlassian answer on this, it's been open for years and really hits NPS for users.....it's a basic requirement for usability to avoid boards with large numbers of columns.

Can someone at JIRA please comment the progress on this? What is the reason to not fix this? Is it very hard technically?

It has been reported as bugs as well but they are closed, I hope the bug comments are added as up-votes to this issue as well?

Yet another Atlassian bug that's desperately needed and have been open for more than 5 years. This makes WIP limits in a Kanban project very difficult to use properly. For a "Specify" column, where the "entry" status is Specifying, and the "done" status is Specified, you want the WIP limited so the folks doing the specification don't keep specifying/pulling cards off of the backlog if the "Implementation" step is already at capacity. Using two columns with WIP limits in each doesn't work either, because the "Specifying" tickets can't move to "Specified" when they're complete. Pretty much the only way JIRA Agile seems to be usable in this case is to use the keyboard shortcut "." and manually transition, which is pretty ridiculous, especially when this was possible before.

I ran into this recently in conjunction with trying to close a sprint.

When closing a sprint, all "completed" statuses have to be in the right-most column so that issues are not put back in the backlog. We have complete status of "Deployed" and "Validated". We don't care to "validate" every ticket that gets deployed.

In this situation, it's impossible to drag from Deployed to Validated using our scrum board.

the solution for many problems related to transitioning the issues in the board is that the target status should always be displayed, when dragging on the same column or different column, which is not the case now (see issue below).

folks, could you please vote the following related issue that addresses the root problem : https://jira.atlassian.com/browse/JSW-10465

For me it generally works as expected, with one very specific bug that may be the actual problem people are trying to report:  which status you choose within the column is dependent on the mouse position within the card being dragged rather than the card area.  If you group into swimlanes, such as by project, the draggable area within the swimlane is restricted by the longest column in that lane.  So if you only have one card in that lane, it can't move vertically at all and the mouse position will be constrained to whatever status is horizontally across from where you picked the card up.

One potential fix would be to allow fullscreen motion for a card being dragged (but not allowing the drop unless it's in the same swimlane) so that it can be dragged over the desired status in this scenario.

This feature would increase efficiency on the board tremendously. Having multiple statuses in a single column is great for reducing the # of columns needed. Plus, the green dashed lines already show in the Done column; we just need that enabled for all columns.

+1

This feature would unclutter our kanban board. It would allow us to add states to 'ToDo' that can be used to track the issues' readiness for work to start.

Please consider implementing this feature, there is a lot of requests for it.

Thanks!

I support the desire for this "feature-flaw". It may not be a direct bug, but is certainly something you would expect should be possible.

Otherwise your issue transition pattern will be clouded by developes moving issues to different columns on the board in order to get it back in the same column with a different status. 

Atlassian - Please step up..

I am almost certain that this feature existed once before in an earlier version. Why was it removed? Resorting to keyboard shortcuts to manipulate tasks is not an acceptable workaround. It should be obvious from all the votes on this issue that many people don't work this way.

How to implement it? As suggested you could use a keyboard modifier - since you're assuming we're using the keyboard shortcuts already.

Or, split the column in half, one for ranking and one for multiple transitions with color-coded differences. Your suggested workaround is to simply add more columns to cover all of our statuses, so column width clearly isn't a concern. (Just how wide are your monitors, anyway?)

Or, pick another solution and let the community vote on it.

This now gets added to the long list of features that the Atlassian team has deemed "not worth it" even though there are customers asking for it.

+1 This would make users not look for other products as it's quite a common request. 

+1 we really need this feature

same as all the peoples here.
+1 to have this feature added please.

This feature would be great. Hopefully it gets some movement from Atlassian.

This feature is an absolute no brainer and would make he tool way simpler for users.

Also agree this is a highly desired feature request!! We have several more columns on our board than we'd like because on the need to be able to drag and drop.

Also is there a improvement reported on status label to presented as Epic label does? It would greatly improve readability of the backlog and active sprint.

This is a must. Otherwise we are left with additional 3-4 columns which are painful to watch (sharing status over a virtual meeting causes our eyes to bleed after prolonged time of watching microscopic cards). Other solution would be to make cards dimension fixed and enable scrolling (like trello does). I cannot imagine that .dot shortcut as best solution from usability point of view.

P.S Furthermore you are not letting us create more TODO (blue) and DONE(green) type of columns and we have different statuses which match those types!
P.P.S Ranking is maybe useful in first column to be able to see which task should go first. Later nobody cares as tasks are already assigned to different people who themselves track their rank. If you do not agree then explain to me what is the meaning between closed issue ranked higher than another closed issue? Who is going to make business decision on this fact?

+1 from me for my personal use.

Use Case; I use JAG to track bills and the "Done" column is mapped to two statuses, "Paid - Pending" and "Paid - Complete"

Would be awesome if I could move an issue from "Paid - Pending" to "Paid - Complete" without having to open up that issue and transition it.

We would also be very interested in this feature.

As mentioned above, i think drag & drop should be for transitioning issues, while you could use a modifier key for ranking.

Kasper Hendriks
iBOOD.com

This is the most annoying in RapidBoard when you don't have ability to modify the workflow on jira.

Reopening this for further discussion, however we cannot provide any guidance at this time as to when, or if, we'll be implementing it.

Regards,
Martin
JIRA Software

This issue should be revisited by Atlassian. This was literally the first question my team asked me when I showed them the board & workflow we had setup for the first time. Please reconsider how teams should use this action. ( Our workflow has a half dozen "in progress" states – we can't have a column for each, it would be way too messy. )

I would like to add another vote for this issue. It would be a huge improvement and I second the comments before mine.

Hi Atlasian, a way of doing this easily for people would be:

If an issue has transitions within the same agile column, then display a button on the issues tile that gives a dropdown list of the available transitions within that column.

If an issue doesn't have transitions within the same agile column, then dont display the button.

That way enough info is being presented to the user for them to visually see what is available for them to then make a choice.

For now, I'll have to survive with the "." shortcut - but that is only really usable if you know the transitions.

Hello Atlassian,

I would like to second this request as well. For the sake of better visibility, I ended up grouping statues in columns, but now I have a sub-par usability by losing the drag and drop in between status sharing the same column.

I believe the point of the boards is to both provide better visibility and better usability (through drag and drop for transitions), and allowing transitions within the same column would benefit users with longer workflows, who right now have to chose between visibility or usability when configuring their boards.

Thanks

Hi Atlassian Team,

I've been searching for this exact feature over the last few days. Being able to simplfy our board (We have 6 columns at the moment) to just Next, In Progress, and Done would be amazing.

Could you consider reopening and addressing this? There are a number of squads that would benefit from being able to do this where I work. It seems the same issue has been raised multiple times by lots of different folk:

https://jira.atlassian.com/browse/GHS-11677
https://jira.atlassian.com/browse/GHS-10434
https://jira.atlassian.com/browse/GHS-9720
https://jira.atlassian.com/browse/GHS-10529

Thanks.

Transitioning issues to different statuses within the same column would be very helpful and relevant to most development processes. As per the standard JIRA status definitions, Resolved refers to the point where development is at a point of completion (and usually ready to be tested) and Closed refers to the point where you are satisfied with all work (the work has been tested and will be deployed). To not allow for an issue to be moved from Resolved to Closed within the same 'Done' column seems counter intuitive.

I would like to see this feature added in the near future.

Many thanks for reporting this issue. Realistically, we are not planning on addressing it in the next 12 months.

We recommend using columns that map your workflow horizontally. Transitioning an issue vertically as mentioned is not something we have optimised for, and it would not be immediately obvious which status an issue is in.

Regards,
JIRA Agile Team

Please read this - your approach to ranking vs transitional is not feasible in real world circumstances.

Rank is only as important as the plan it is associated with and when that plan goes out the window as it does regularly in the real work then transitions become even more important to move the appropriate work ( not the ranked work) through to Dev and QA to get that code out the door to customers.

So if Citi or some other fortune 100 company tells you get that feature out the door - they are going to get their way in order to keep a high profile account of which our company has many.

Being realistic is more important I would argue than operating off of theory - theory does not pay the bills.

so we really do need this request and to transition as needed.

More importantly as well is to have a complete relation from the workflow to GH and that is not the case today if you were to query Tyler or Gary at your company.

Transitional states have to be tricked out in order to have multiple states (at times depending on what your doing) and the system fields are also no part of this transitional GH State and should be i.e., reopen does not appear as an option and has to be manually updated rather than using the GH GUI.

So when can this request be delivered would be my next question - please call me with concerns.

I agree with this, the dragging action throughout the board is to support transitions, and even allows for choice between different statuses when moving to the new column. The best thing to do would be to continue that interface with the user. For example, if I drag from "To Do" to "In Progress 1" instead of "In Progress 2" (both in the same column), how can I correct that choice? The only way is to drag it back and forth, instead of just dragging it downwards.

Hi Nicholas,

I was sure you've considered this already. I believe one way is to enforce a modifier key (Shift, Ctrl, Cmd etc) for the ranking operation and leave the plain drag for transitioning. By adding the modifier you prevent also accidental ranking which is not that uncommon Now that ranking is audit trailed you can endup with quite a few unintended entries.

Cheers,
Aggelos

Hi Aggelos,

One issue we have with the implementation of this is how to distinguish between a drag to rank and a drag to transition in that column. At this stage we have elected not to support drag to transition within a single column and support the ranking instead.

Any thoughts as to how we could address this?

Thanks Aggelos,
Nicholas