Just doesn't work?

[Bjorn Stabell]

I've been trying to use the tool, and though everything looks fine -- i.e., it says the copy was done -- I can't find the copied project in the new workspace anywhere (and I've tried to search for tasks that I know should be in the project).

My Asana usernames are bjorn@... - perhaps you can see something in your log files regarding this copy?

[Izac Hancock]

Same issue for me.

[Mike Houston]

Hi, is it still failing for you? I've run a test on a couple of my own workspaces and don't see any errors, and the projects are copied successfully. Maybe there was a glitch in the Asana API, since they were releasing their new Calendar feature?

If it still doesn't work I'll do some more investigation and try to display some more debugging information to find out why it doesn't work for you.

Mike.

[Bjorn Stabell]

No, it still doesn't work. It pauses for about 10s, then returns "Done". If I already have a project with the same name in the new workspace, it will claim to copy to a project name with 2 appended to it, which seems reasonable, so it's definitely correctly accessing both workspaces. But, eventually there's nothing to be found in the new workspace..

[Mike Houston]

I've made some changes, and you can now display debug output by visiting the following URL: http://asana.kothar.net/?debug=1

This will print the result from the API after each call to create a new task. Can you run the new version and check what the server response is? It works fine for my test projects, so I'm not sure what's causing the problem with yours.

Mike.

[Bjorn Stabell]

Mike,

I've attached the most significant parts of the output below...

[Bjorn Stabell]

Any thoughts on this?

[Mike Houston]

Hi Bjorn,

I've updated the tool a bit, and now include a full trace of the API calls made - you can turn on that setting with http://asana.kothar.net/?debug=2. If you still feel like giving it another try, let me know if it works, or if the debug trace is more helpful than it was before.

[Bjorn Stabell]

Mike, it seems to work now! The only functional difference (besides the verbose debug output) was that I was prompted to select a team for the target workspace, which I guess is a new feature?

[Bjorn Stabell]

Mike, there's one major drawback that's probably worth mentioning:

• Doesn't re-upload attachments, just links to the old attachments - this means that if you delete the source project/task, the attachments will be deleted for good too

And some minor ones:

• Copies history as comments (I guess that's the only way to do that only way to do that?)
• Doesn't copy ownership (I guess can't do that since members may be different, but in some cases it's just a reorganization so the members are the "same")

[Mike Houston]

Glad it's fixed the more obvious problems for you!

Good point about the attachments, I've opened Issue #5 to cover that. I will see if there's an easy way to do do it without caching a copy of the attachment on the server, but that may be the easiest way to start with.

The history issue is unfortunate, but the 'Stories' API won't let you create history entries directly, only comments.

What do you mean by ownership? I made a quick check of the code: it's definitely supposed to be copying the assignee from the old ticket, so do you mean something else? I'll run a few tests to make sure it's doing the right thing.

[Bjorn Stabell]

Okay, sounds good!

I have to try some more regarding the assignee - maybe the project I tested on didn't have assignees. I just figured it would be hard to do since there may be different users in each of the workspaces.