wekan / Tickets / #799 Add feature: Import/Export Trello/Wekan board to/from Sandstorm Wekan.

Anonymous - 2017-02-08

Originally posted by: xet7

From @tml on January 18, 2017 16:14

With the Trello purchase, I suspect this might be something that a number of people become interested in rather quickly.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2017-02-08

Originally posted by: xet7

@tml

In standalone Wefork it's already possible to import Trello export JSON files, including attachment images. For example using VirtualBox appliance at https://wekan.xet7.org

This feature is not enabled for Sandstorm Wefork.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2017-02-08

Originally posted by: xet7

From @ocdtrekkie on January 18, 2017 16:20

If the import from Trello requires actually logging into Trello, rather than importing like an export file, that'd probably be why, since it requires a network opening to do, and Sandstorm sandboxes the application. Future updates to Sandstorm should make this easier to do securely.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2017-02-08

Originally posted by: xet7

From @tml on January 18, 2017 16:30

@ocdtrekkie I have an export file from Trello, and a standalone Wekan knows how to deal with those; there's just no opportunity to provide that information to the Wekan grain created by Sandstorm.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2017-02-08

Originally posted by: xet7

Checklists are not imported yet, because that feature [#11] is not yet merged to Wefork. Some other features can be missing also.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2017-02-08

Originally posted by: xet7

From @ocdtrekkie on January 18, 2017 16:32

Should definitely tag @dwrensha on this one then.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2017-02-08

Originally posted by: tml

This seems to be a duplicate of [#800]?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2017-02-09

Originally posted by: xet7

@tml

Thanks, I closed [#800] now. Duplicate came when I used https://github-issue-mover.appspot.com/ to move issues from Wefork to Wekan

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2017-02-10

Originally posted by: xet7

@FiloSottile said at [#549]
I'd love this, too. My understanding from [#113] is that [#430] should make this possible.

I have not checked those yet.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2017-03-24

Originally posted by: brevilo

If it means anything: +1 👍 Will use Wekan (via Sandstorm) as soon as this is possible.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2017-05-19

Originally posted by: ajrossnz

Really looking forward to this. As wekan on its own doesn't have LDAP, we can't use that, so waiting on this feature before we go for implementation here.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2017-06-04

Originally posted by: xet7

@ajrossnz @brevilo

Please do not wait. In Open Source, although current code is available for free, the way to use it in your company is to have a programmer in your company implementing missing features and submitting them as pull requests.

According to Open Hub, Wekan code is only about 7000 lines so it's very small when comparing to other software. With git history viewer like gitk it's possible to see how different features are implemented.

To implement this, check current features for exporting and importing, and have the feature enabled in Sandstorm by using environment variable isSandstorm = true like is at wekan/sandstorm.js .

In wiki there is Developer Documentation.

Thanks!

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2017-07-16

Originally posted by: xet7

Currently dropdown menu on Wekan looks like this:

In addition to https://github.com/wekan/wekan/pull/1134 for Import to work on Sandstorm @GhassenRjab would need to add:

1) Check that isSandstorm variable is true https://github.com/wekan/wekan/blob/devel/sandstorm.js

2) Add to board menu above Export also Import

3) When Import is clicked, there would be paste screen and warning above it that imported board will delete all existing data on board and replace it with imported board.

I don't know is mapping of imported board users to Sandstorm users somehow different than in standalone Wekan. @dwrensha do you know about this?

Also on same menu where is Outgoing Webhooks. Is there a way to make it work on Sandstorm?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2017-07-22

Originally posted by: xet7

@ocdtrekkie @dwrensha @kentonv

On menu above there is Archived boards.

Currently on Wekan the All boards link is hidden, and only one board is used on Sandstorm.

When importing new Wekan board, should current board be archived, and new board be made visible?

Then on Board menu / Archived Items there would be Cards, Lists and Boards.

Or should there instead be:

All boards page and similar functionality like in standalone Wekan?

Ability to copy cards/lists etc to some other board on the same grain, and also to other grain at Sandstorm?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2017-07-22

Originally posted by: ocdtrekkie

The ideal Sandstorm way to handle multiple boards would be to continue with Wekan only containing one board, but that trying to copy cards or lists to another board would bring up a Sandstorm powerbox to select a destination Wekan. That ensures the security isolation continues to work well, that people who can access one board can't tamper with another board even if there's a security issue.

If you can archive the old board when importing a Wekan board, that might be a smart choice just in case someone ignores the warning and overwrites the content accidentally. Presumably someone could dig into the grain backup and pull the lost data out of it with some effort.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2017-07-22

Originally posted by: xet7

@ocdtrekkie

I think in that case, that when importing new Wekan board:

current board should be archived

new board be made visible

on Board menu / Archived Items there would be Cards, Lists and Boards, with options to restore and delete board.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2017-07-22

Originally posted by: xet7

Also when restoring archived board, current board should be archived. Only deletion is from archived boards.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2017-07-27

Ticket changed by: xet7

status: open --> closed
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2017-07-27

Originally posted by: kentonv

FWIW, the ideal way to handle "imports" on Sandstorm would be to have a separate new-grain action. Currently there is only "New board", but you could also have "Import board", which launches directly into an import UI. It feels a bit awkward to create a blank board and then import over it.

However, I'm not sure it's worth your time to try to make this work.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2017-07-27

Ticket changed by: xet7

status: closed --> open
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2017-07-27

Originally posted by: xet7

Hmm, I don't know yet. There will be additional import export options and they could be more easily found on Wekan Board menu. AFAIK something (maybe restoring board?) was already left out from Sandstorm import export because of complexity to implement it.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2017-07-27

Originally posted by: ocdtrekkie

Currently EtherCalc also overwrites the existing content as the import method. It's probably not ideal, but its better than nothing for now.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2017-07-27

Originally posted by: ocdtrekkie

As a note, if the packaging hackery got smoothed out so people could build test packages for Sandstorm without David, it'd be easy for me to help people through setting up the separate Sandstorm command and such. But as it stands we have no way to test that.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2017-07-27

Originally posted by: xet7

Automatic builds for Sandstorm would be nice, like there is currently for Docker and Ubuntu snap edge.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2017-07-27

Originally posted by: ocdtrekkie

In order to do that and it work in production, we'd also need to switch the signing key for Wekan away from David's key (might be prudent anyways since he doesn't seem super interested in building this regularly), and your build server would need to have the new key.

But at the very least, if we had a routine/reproducible way for people to build test packages of Wekan for Sandstorm, it'd be possible to test Sandstorm features on it. (There's more I'd like to do, like enabling access to the API and stuff. Someday hopefully using the Powerbox to move cards and lists between boards, etc.)

If I could package Wekan, I'd be more than happy to work with anyone who needs help implementing Sandstorm features, like a separate "Import board" flow.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Add feature: Import/Export Trello/Wekan board to/from Sandstorm Wekan.

Milestone

Searches

Help

#799 Add feature: Import/Export Trello/Wekan board to/from Sandstorm Wekan.

Discussion