Hi guys,

I know it's a bit old 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!

When are you planning to release this issue to production version?

I am resolving this as a duplicate of the linked issue. Please watch that one for updates.

Yes, Martin. I'm talking about the issue described at https://jira.atlassian.com/browse/GHS-8801

This issue has nothing to do with what you have been explaining that you can't transition the status of an issue by vertically moving it within the same column. Using the '.' works just fine.

Are there going to be a fix for https://jira.atlassian.com/browse/GHS-8801 any time soon?

Atlassian, to lessen confusion in future, might I suggest a doc update to

https://confluence.atlassian.com/display/AGILE/Using+a+Board
namely the Note: section of Work Mode by adding something that describes what essence of what you shared in this ticket?

Other candidate pages for Notes are
https://confluence.atlassian.com/display/AGILE/Configuring+Columns
https://confluence.atlassian.com/display/AGILE/Using+Work+Mode
https://confluence.atlassian.com/display/AGILE/Transitioning+an+Issue (and perhaps respond to comments asking our question, there as well)

Thank you for considering.

Martin, given this Board design, we have some teams who in fact have 1 col per state. Most teams though have simplified the view by associating workflow states of similar kind, to one column. Our workflow is very lightweight, so as soon as more than one state is in a column, we will be using alternative ways such as "." to move. Again, we're not seeing why Atlassian is forbidding a drag-and-drop within a column but it is what it is, so we will use alternative means. Thanks for highlighting the "." technique.

laith.albataineh are you referring to the bug as described at https://jira.atlassian.com/browse/GHS-8801

tim.arthur I'm glad the "." function will help, but I would recommend using columns that map your workflow horizontally. Transitioning an issue vertically as mentioned is not something we have optimised for, aside from drag and drop there it's not immediately obvious which status an issue is in. I don't think adding just the drag and drop would offer a good solution, I do think using separate columns where it makes sense is a better one.

I knew the workaround is to use the '.' keyboard shortcut to change the task's status to any other status that's in the next column. This appears to be working - the task is moved over to the next column and the status is updated successfully.

It's just the UI bug that needs to be fixed since the user is prompted to drop the dragged card into whichever status within the next column. I hope this clarifies what the issue is.

Note: I'm seeing this on the 'on demand' version.

Thanks for the clarification, Martin! I think there is a misunderstanding.

In your last comment, you said, "...This issue is regarding the ability to transition a card to another status in the same column it is currently located." I think that's where i agree and disagree with you.
I'm totally ok with the current ranking functionality by moving a card vertically.
I'm also ok that, currently, a user can not transition status by moving cards vertically within the same column regardless if a column has multiple statuses within it.

The real issue (UI bug) i initially reported was the fact that the user is prompted (blue drop zone areas (status) appear) when a card is dragged from one column to another which happen to have multiple statuses. The issue is that while dragging the issue to hover over whichever status within the next column, the vertical movement is restricted and not functioning correctly. I can not move the mouse vertically high or low enough to cover all available statuses to drop the dragged card in. Also, if there's only one task in a story in one column, and the next column have 4 or more statuses, the board's UI row won't expand enough to show all available statuses. Only the first two show upon dragging a card over, and the rest of dotted blue status areas are cut off. I think the resolution should be that the board rows should expand enough to show all statuses within the next column over.