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.

Correction- I see "," works when in an issue, as stated in the blog.

Atlassian,
We can use the "." function. I was not aware of that. Thank you. (BTW, nothing happens when using "," from the board.)

Please though-- can you tell me is your decision based on difficulty (e.g. may not be doable with current technology), or is it more a matter of principle in that the drag-drop only works between columns (just seems so odd to me to forbid a same-col move). Knowing that help me message to our very large install base. Using the "." function can avoid wasted effort of card-moves, ensuing emails, and questions by those not familiar with this intricacy.

As a customer, I interpreted item 3 differently.
Tim

laith.albataineh I think you might have misunderstood this issue. There has been no change in the feature to move an issue from one column to another column with multiple statuses, this is still available. When carrying out that action in a single movement the card is dragged across to a column highlighted as available (blue then green) and then if there are multiple statuses they are named and drop-zones appear. This issue is regarding the ability to transition a card to another status in the same column it is currently located.
The video clip you refer to shows this existing functionality (I'm assuming ~ 20 to 22 minute mark as I skimmed it, it's a 55 minutes clip), this still works as expected.

This issue is therefore a feature request, to change the vertical drag and drop functionality from ranking to transitioning to a different status in the same column. We are not planning to add this feature to JIRA Agile at this time, we do not see this as a case we will optimise at present, and the goal can be achieved using issue actions or keyboard shortcuts as mentioned above.

Correction: Sorry, It was not JIRA team who presented JIRA Agile in the link i provided in my previous comment. It's always a good idea to see who published the video before watching it. I was a bit excited i guess. But how was it working for them back in February and it's broken now?!

You're welcome, Martin. I'm a big fan of JIRA and I've installed it and administered it twice in the past. This is another attempt to switch my current employer to use JIRA instead of Rally. I'm glade i tried this out before demoing JIRA Agile to my team and management. The problem i had is when transitioning tasks from one column to the next, and to a specific status within the targeted column. The dragged task can only move up or down so much while I move the mouse vertically within that column covering 1 or 2 statuses from within that column at most. In fact, I had to add three tasks for each story in order to be able to access all five statuses in the next column. And even then, I would have to drop the task back where it was and then grab it from the upper right corner if i want to reach the top most status in the next column.

The one problem i'm still having is why the false advertisement?! It's totally unnecessary. If the goal is to sell JIRA Agile, then be sure to present functional working features. If a feature is really not ready or unstable, it should not be advertised. During this presentation https://www.youtube.com/watch?v=CdgzDrjdTyo (minute 34:20), JIRA team presented JIRA Agile and it was heavily advertised using drag n drop across columns and vertically to a certain status within the targeted column. I thought to myself that this is an awesome feature and management would just fall in love with it. Not a single person in the presentation made it clear that this functionality is not functional or supported! On the contrary, they made it seam that this is one of the core basic functionality of a JIRA Agile scrum board.

Despite the fact that you think this is not a bug, you can't prevent the user from dragging and dropping into certain status areas within a certain column (because you enabled the user to do so). The users will experience the UI bug i reported and will be disappointed. I think JIRA Agile should finish what they started and fix the UI bug. Otherwise turn the 'dropping into sub-statuses' off so that you won't disappoint any more customers.

This, sir, is a major bug indeed and it's totally not worth screwing with JIRA's public image and promise for such a stupid bug. Please fix it fast. Your efforts are much appreciated...

This is not at odds with our company values. I have described how the use-case is not the one that the product is optimised for and there are ways to achieve the goal via a couple of clicks rather than drag and drop.

We cannot build everything that our customers request, we have a prioritised backlog and work through the items of highest value and where they make most sense in our roadmap at a given time. We have an open backlog, this one, which allows customers to openly describe or discuss their requests but this does not mean we can fulfil all of them. The customer requests do influence the decisions but they are not the only factor.

It is good to see Atlassian make a statement on this.
It is at odds with https://www.atlassian.com/company/about/values, particularly item 3 in the list.
Customers have asked for this, persistently. Should that not influence the decision?

Many thanks for reporting this issue, however this is currently working as designed (so is not a bug) and is not something we plan to add to JIRA Agile at this time.

JIRA Agile is optimised for transitioning an issue using drag and drop across columns, as noted dragging to a different status in the same column is not currently supported. The primary action for a vertical drag is to rank the issue.

If a transition is required between multiple statuses in a column then drag and drop cannot be used for this purpose, the ways to achieve the transition are to either use issue actions (available via the cog or '...' button/menu on the detail view for an issue, or on the JIRA View Issue page) or keyboard shortcuts ( http://blogs.atlassian.com/2012/08/jira-tip-of-the-month-dot-and-comma-dialog-shortcuts/ )

I would recommend splitting the statuses to multiple columns if drag and drop is necessary, or continue as today but using issue actions or keyboard shortcuts.

Regards,
Martin
JIRA Agile team

p.s. cjackson1 sorry to hear about the kittens

Hmmm......That will not work either. Is there any way to change the status of a ticket from one to another within the same column by not drag and drop but perhaps a right click and change. Currently the only way I see it is by looking at the ticket detail view next to the board when the ticket is selected from the board, click on the button with 3 dots on the top right hand side, click on "More Actions..." menu item and then select the next status from the drop down from the popup dialog. Is there a way to show the drop down that allows changing status in the detail view page itself?

We don't... we create a "sub-board" (not really as sub-board, it is just a board) I'll try to give you an example, I don't have the real board in front of me, so it won't be perfect.

So if your columns are:

Main Board
--------------
Open | Creative & Requirements | Ready for Development | In Development | Complete

and "In Requirements" has the statuses: Creative, Business Requirements, Client Review

So we create a second board for the other audience to use:

Creative & Requirements Board
----------------------------------------
Open | Creative | Business Requirements | Client Review | Ready For Development

Sorry that this is a poor example of an Agile process, but you get the methodology...
Sadly, the problem is that this only OK when you have an audience that doesn't need the whole board... and only makes things a little less painful. It doesn't work in all of our use cases. Thus the aforementioned pandemonium.

Chad - How do you create "Sub-boards" within Columns? May be we can look at that as a work around till a better solution is available

Wow that's pretty bad. Not that bad, here, yet....

Again Tim, you are dead on. We've had to create "sub-boards" for managing tasks within a single column, what utter nonsense. People are complaining, hell is raining down upon our heads, puppies and kittens are on fire and there is chaos and death in the streets.

Atlassian – let me comment further... I know this might seem like a "nice to have", but is really causing us to redesign our entire use-case with JIRA Agile, and not in a lighter, better way. The whole beauty of boards in being able to consolidate multiple statuses to one column, can't be used. Instead, we need to create a board having one column for each status. The other alternative we have, and it is not popular, is for a user to drag a card back or forth to another column, first. That's wasted effort, and generates mail and more wasted effort.

Hi - We are trying to convert our groups here from using the traditional JIRA to start using the JIRA Agile boards. I ran across the same problem where dragging a ticket from one status to another within the same column was not allowed. This is a major road block for us to move to JIRA Agile. Is there anyway, this can be escalated to get into a patch? We are currently using JIRA version 6.0.3

You hit the nail on the head my friend. The fact that this is assigned a "minor" priority is insane to me. This seems like it should be basic usability.

Atlassian, this doesn't reflect well on JIRA Agile. Can you offer a date to resolve?

This is a pretty huge issue for people who are using agile boards with more complex workflows.

Is it likely this issue will be addressed in the near future?