[bcmParticipant]

Just noticed there’s a new release (14.0.0).
I tried to replicate the above issue but the problem remains.

Is the work item still on your roadmap?

Regards,
Bruno

[bcmParticipant]

Hi and thank you for fixing the “newColumn” issue on your latest release

I have a requirement that need to move images from a column to another columns between multiple kanban tables.
The newColumn is now populated however the ‘itemRenderer’ property is not being copied over.

http://jsfiddle.net/bmosca/3u1h7g9L/5/

On the example above, the image just disappears when moving to a column from another connected kanban table.

Also on that example it looks like I cannot move items from #kanban1 to #kanban5 or #kanban6, the dragged element seems stuck at #kanban4 and won’t be movable further down the screen

Is that something that could also be fixed please?

Many thanks

• This reply was modified 1 year, 7 months ago by  bcm. Reason: missed link

[bcmParticipant]

I tried the example above and I can confirm the issue remains.

When moving an item from #kanban1 to any of the columns which is not “backlog” the “newColumn” variable is not populated on the itemMoved event
Sound like when there are multiple connected kanbans we can only drag items between columns with the same datafield, i.e. “new”.

We should be able to have the newColumn variable filled with the destination column as we do when we move items between different datafields in the same kanban table

Is that something that could be fixed please?

[Author]

Posts