I don't get any blue slots where I can drag a card from one column onto another (scrum board)

[fvillalba_LL]

According to this page: https://confluence.atlassian.com/jirasoftwarecloud/transitioning-an-issue-777002790.html

... I should be seeing something like this: 

when dragging a card from one column onto another (scrum board)

However, I don't see any (in fact, nothing happens)

I don't think it's a permissions issue since I have another board where this seems to work (although in that one I'm mapping just one status to one column)

I've also verified that "transition issue" is enabled at an Application level.

Can you help me sort this out?

[Alexey Matveev]

Hello,

Make sure that there is a transition from the current status of the issue to the status, which is mapped to the column, to which you are trying to move the issue. You can open the issue detail view and see, if there is a button, which lets you do this transition.

[fvillalba_LL]

Ha. You may be right... I think the problem is the statuses I can move the issue onto are mapped onto the same column as the issue's current status.

What to do in such scenario?

[Alexey Matveev]

I would add a new column and mapped the status in the same column to this new column

[fvillalba_LL]

That's precisely the solution I'm trying to move away from.

Our WF is complex, several status and multiple transitions (yet still clean :-) ).

The "alternative" board I mentioned on my original post precisely takes that approach. However, JIRA's usability degrades significantly due to the vast number of columns, which essentially make the cards unreadable

(side note: how difficult could it be adding a horizontal scroll bar and ensuring a minimum width for all cards, JIRA? come on... there are commercial add-ons that do this)

Also, and I'm trying really hard not to go off-topic here, if at the very least the transitioning buttons would show up when clicking on a card, then drag-and-dropping wouldn't be a show-stopper... but that doesn't seem to work, either.

[Danyal Iqbal]

The "alternative" board I mentioned on my original post precisely takes that approach. However, JIRA's usability degrades significantly due to the vast number of columns, which essentially make the cards unreadable

(side note: how difficult could it be adding a horizontal scroll bar and ensuring a minimum width for all cards, JIRA? come one... there are commercial add-ons that do this)

An Addon is one thing but scalability in-general is a different beast all together. I think this feature is being blocked by other scalability issues.

[Alexey Matveev]

If you want to make less columns then you should make less statuses.

[fvillalba_LL]

Alexey: I would have to work for a different company in order to be able to use less statuses :-)

As you can imagine, our WF caters for our business needs and we've already simplified it considerably. Simplifying it further would essentially challenge our teams' productivity (and effectiveness) altogether.

The problem is not in the WF, it's in the tool (unfortunately, as I was the main sponsor of JIRA's adoption in my organization)

[Andy Heinzer]

Hi Freddy,

I understand that you are not able to transition an issue into another status using a particular scrum board.  Could you share with us the filter being used for this board?  I ask because if your filter is selecting issues from multiple projects and/or multiple issues types it is very likely that some issues will have different workflows.   This can be important to understand why transitions might not be working the way you expect here.

Does this problem happen for all issues on this board?  Or is it only some issues types?  Or is it only issues from some projects?

It is possible that some project might have a status like Done, but that other issues form another project either don't have that same status, OR don't have a workflow transition that allows that issue to transition it into that status.

The other aspect to look at would be the specific workflow the the issue(s) that can not be transitioned in this way. If the workflow does have this transition, then a workflow condition could be in place to prevent this.   If that workflow does not have this same transition to that status, then this difference could also account for the inability to make this transition using this board.

[fvillalba_LL]

Hi Andrew,

I think we can safely discard all of the above:

1. This is a sandbox environments where there are only a few "test" tickets created so far.

2. There is only 1 WF for all issue types.

Just fyi, I will be creating a second WF shortly which will apply to a new issue type I will be creating. That 2nd WF will comprehend nothing but a subset of the existing WF's statuses and transitions -- and we will visualize issues of that specific type on a separate board.