jQWidgets Forums
jQuery UI Widgets › Forums › Layouts › Kanban › args.newColumn not set when using itemMoved with multiple connected Kanbans
Tagged: itemMoved, javascript kanban, javascript kanban widget, kanban
This topic contains 9 replies, has 7 voices, and was last updated by admin 3 years, 3 months ago.
-
Author
-
August 10, 2016 at 2:53 pm args.newColumn not set when using itemMoved with multiple connected Kanbans #86466
Hi.
I have 3 Kanbans connected together using connectWith. They work fine and behave as expected.
The problem I’m experiencing is if I drag an item from 1 Kanban to another (e.g. #kanban to #kanban2), when itemMoved is fired, args.newColumn is null. Everything else appears correctly, even the oldParentID and newParentId are populated with the IDs of the Kanbans.
If I drag an item to a different column within the same Kanban (even with multiple Kanbans displayed), then args.newColumn is set correctly.
Has anyone had any experience with this?
I’m calling itemMoved in the following way:
$('#kanban, #kanban2, #kanban3 ').on('itemMoved', function (event) { var args = event.args; var itemId = args.itemId; var oldParentId = args.oldParentId; var newParentId = args.newParentId; var itemData = args.itemData; var oldColumn = args.oldColumn; var newColumn = args.newColumn; ...
August 15, 2016 at 8:41 am args.newColumn not set when using itemMoved with multiple connected Kanbans #86526Hi again,
I assume this topic went without answer because I failed to provide a complete code sample. Sorry, that’s my bad.
Due to the large amount of code, I’ve added it using your (extremely cool) jseditor.
LINK: https://www.jseditor.io/?key=kanban-issuePlease run the sample and firstly try dragging items between the columns in the bottom right kanban (#kanban3) and see the the names of the columns appear correctly in the console.
Next, try dragging items between the kanbans and note the information which appears in the console. In the project I’m working on, I need to display 3 kanbans on the screen and give the user the ability to move items between them, but due to this error, I’m unable to finish this work.
Please could you provide assistance with this.
Thanks
August 15, 2016 at 12:17 pm args.newColumn not set when using itemMoved with multiple connected Kanbans #86542Hi jason_f1,
Thanks for the feedback.
We will investigate this behavior.Best Regards,
Ivailo IvanovjQWidgets Team
http://www.jqwidgets.comSeptember 20, 2016 at 9:00 am args.newColumn not set when using itemMoved with multiple connected Kanbans #87517Hi Ivailo,
Have you been able to look into this yet?
Thanks
Jason
March 14, 2019 at 6:07 pm args.newColumn not set when using itemMoved with multiple connected Kanbans #104345Hi guys,
I have this problem too, it seems that this behaviour haven’t been fixed.
Can u say me how i can “fix ” it ?Thanks, Pablo.
March 18, 2019 at 1:52 pm args.newColumn not set when using itemMoved with multiple connected Kanbans #104383Hello Pablo,
Please, take a look at this example.
I tested this example and it seems to work fine.
You should check is there such columns relevant as the columns in the previous jqxKanban.
Otherwise, it throws error and brake the widget.Best Regards,
Hristo HristovjQWidgets team
https://www.jqwidgets.comJanuary 19, 2022 at 5:45 pm args.newColumn not set when using itemMoved with multiple connected Kanbans #121381I 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?
January 20, 2022 at 3:35 pm args.newColumn not set when using itemMoved with multiple connected Kanbans #121388Hi bcm,
Thank you for reporting this behavior!
I have created a work item for this use case and we will to fix it as soon as we are able to.
Please, do not hesitate to contact us if you have any additional questions.
Best Regards,
Yavor Dashev
jQWidgets team
https://www.jqwidgets.comJanuary 28, 2022 at 4:29 pm args.newColumn not set when using itemMoved with multiple connected Kanbans #121443Hi 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
January 31, 2022 at 10:09 am args.newColumn not set when using itemMoved with multiple connected Kanbans #121448Hi bcm,
The itemRenderer is a functionality of a specific Kanban component. It should not be copied by moving a task from one Kanban to another as this is like setting a property to another component which could be already being set.
Best Regards,
Peter StoevjQWidgets team
https://www.jqwidgets.com -
AuthorPosts
You must be logged in to reply to this topic.