Export/Import error "No comments is required" in v1.49.1

[sfahrenholz]

Issue

Server Setup Information:

• Did you test in newest Wekan?: yes
• Wekan version: 1.49.1
• Operating System: Ubuntu

Problem description:

• We have an board since <1.46 and starting a new turn. So we exporting the old and want to import this. (around 30 card, 2 swimlanes, 8 Lists)
• We can allocate the users (all green)
• In the next step a Error 400 is showing (yellow box) and the board is not imported.

It would be nice, if there any chance to see whats happend on the import and where is the error. This is the third time, that we have this problems.
i try some analyse for the json, but its correct.. Also remove some values (activities, cards, ..) but there is no effect.. Wekan is a nice board, but more information on this way would be really nice..

[xet7]

If you use Snap, what does this command show after you see Error 400 ?

sudo snap logs wekan.wekan

If you use Docker, what does this command show after you see Error 400 ?

sudo docker logs wekan-app

[sfahrenholz]

This is the log from server
(Ubuntu Server, snap)

[xet7]

@sfahrenholz

I think you are using Wekan edge tag, because you have Wekan version 1.49.1. It has buggy new features like IFTTT #1898 and OAuth2. It would be better if you use some release tag like v1.49 or latest tag.

Anyway, that bug exists in all versions of Wekan. You can fix it manually by opening exported Wekan JSON file in text editor, and replacing:

"isCommentOnly":false}

with

"isCommentOnly":false,"isNoComments":false}

and then importing that Wekan JSON to Wekan.

This bug is because recently I added new feature member role "No Comments" #1861 . I have not fixed this yet.

[xet7]

@rjevnikar

Do you have time to fix Wekan JSON export issue I described in comment above?

[sfahrenholz]

Thanks for the help, i can reported the board.
But there is another 400 Error after importing

maybe this is already important to know...

[xet7]

Thanks, I have seen also that, but forgot to mention. If all members are mapped, usually when that happens, board is imported anyway.

[rjevnikar]

@xet7 I'll work on it as I have time.
In the mongo shell you can use:

db.boards.find().forEach(function(e){var t=e.members;t.forEach(function(e){e.isCommentOnly=false}); db.boards.update({_id:e._id},{$set:{members:t}})})
db.boards.find().forEach(function(e){var t=e.members;t.forEach(function(e){e.isNoComments=false}); db.boards.update({_id:e._id},{$set:{members:t}})})

Needs to be written into migrations and the import process still

[crispybrain]

@sfahrenholz

I think you are using Wekan edge tag, because you have Wekan version 1.49.1. It has buggy new features like IFTTT #1898 and OAuth2. It would be better if you use some release tag like v1.49 or latest tag.

Anyway, that bug exists in all versions of Wekan. You can fix it manually by opening exported Wekan JSON file in text editor, and replacing:

"isCommentOnly":false}

with

"isCommentOnly":false,"isNoComments":false}

and then importing that Wekan JSON to Wekan.

This bug is because recently I added new feature member role "No Comments" #1861 . I have not fixed this yet.

Worked for me! Thanks