I am trying to set up a simplified workflow where a ticket can be moved through several statuses in a single column. I have the sections set up but once an issue is in a column, the statuses disappear. Here's a screenshot of the column setups:
And here is what happens once an issue has been moved into that column - the statuses no longer exist (it was moved into the top one but now no option to move it down the column).
Need this too. I actually makes it necessary to do 4 clicks to move a ticket to another status. For example if you have a ticket in the analysis phase, the ticket could go several times back and forth for questions between a business analyst and a developper before everything is clear. It would be really, really nice to have this feature as it would make the greenhopper board even easy to use for executives and as a working tool in meetings.
Is this enhancement request still open? As I'm still not able to change the status within the same column of a kanban board by drag&drop, as we also have several status mapped to one column.
The solution could not be so hard, as it is also possible to drag&drop an issue to another coulmn wihich has several status attached.
We also have this problem. We have simple Agile Board (3 columns) and multiple statuses mapped to each column. In the 2nd column we have "In development" and "RTD" (ready to deploy) statuses. From "In development" status we can make transition to "RTD" and "Resolved", but in the Agile board the former is not available because it's in the same column.
From my point of view this makes no sense: since workflow supports this transition, it should be possible to make it via drag'n'drop.
Creating another column and re-mapping RTD is not proper solution because we don't want to complicate Agile board view. Would be good if transitioning between statuses in the same column were possible.
This is my #1 headache with JIRA right now. Our columns represent high-level states (e.g. "In Development") but that column represents multiple states (e.g. "In-Progress", "Code Review"). Using the actions menu to change the status is very clunky compared to dragging and dropping into the state fields of a column.
Note that you can drag to specific state in a different column, so it seems like the generally functionality to support this feature is already in place.
I am likewise very keen to see this functionality added. The workaround mentioned does work however, when doing Sprint Planning it's greatly time consuming. This hampering ease of use for our business users, to the point that they wont do this in their own time, and this is affecting adoption of Agile.
A kanban board does not work without this feature. Without being able to "pull" issues from a column to another, the kanban agile design is broken in JIRA. Each column must have a maximum number of issues, so i cannot split the "in-progress" to two columns, since i want both to have the same issue count limit, to create bottlenecks.
This missing feature of not being able to move between statuses in a single column might have me consider dropping JIRA for other alternatives.
Much as I'm an Atlassian fan-boy, I do still see some of their failures past my free-t-shirt-and-beer haze.
They have still not done anything to allow us to move issues between status in the same column. They've also closed most of the improvement/request/bug reports that cite it with a "won't fix" message one way or another.
We're not going to get "transition within the same column" for the foreseeable future. Which really annoys me because the code changes to do it really are not hard.
That is why I'm quite negative about it as well. There's no logical justification for it.
A lot of stuff that looks useful but Atlassian decide not to do is justifiable for all sorts of reasons - bad practice, confusing for users, the coding would be huge for little benefit, it's an edge case most people don't need - all valid understandable reasons. We might not like them, but we can understand.
But this one is not hard in coding terms, is not a bad practice or bad idea and is totally intuitive for the users. It's useful, sensible and more intuitive than the current behaviour.
Atlassian have not justified why they are not going to do it as far as I can tell, so I have exactly the same question. They have not explained why.
I too am trying to solve this problem. I'm using two separate workflows for each project so that we can handle bugs slightly differently than we handle stories/sub-tasks in that we add a "resolved" step, used by the developer for bugs to indicate that it's ready to be verified by the QC team. I do not want to add a fourth column to my board as it will simply clutter the board for non-bug issue types. I've created the two workflows and associated the task types with each workflow and am able to transition issues, but can not transition issues from "in progress" to "resolved" within the same column using the drag-and-drop function on the board... rather, I have to use the menu option (More --> Resolved) to complete the transition from one status to another when the statuses are in the same column. Does anyone have any ideas?
I don't know if this is still of interest, but at least in JIRA 7 I can do the following:
We need this, too. It is really very stupid that moving into another column offers this option but not moving within the same column.
We work in a multi project team. Not all projects use the same workflow. So we don't want to work with dozens of columns to get this working...
Atlassian - please add this feature.
This approach requires you to have the JIRA administrative rights. The main aim of this article is to help you achieve an organized, easy-to-maintain workflows in your JIRA instance thereby, reducin...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs