Error creating task - No matching route for request

Issue #3 wontfix
Rico S. created an issue

I wanted to transfer some projects from the Personal Tasks to another workspace and I get the same error for each task: Array ( [0] => Array ( [message] => No matching route for request ) ) The project has been created but no tasks in it.

Comments (8)

  1. Mike Houston repo owner

    Hi Rico,

    I can't reproduce the problem, although the error message looks like a common API error which would imply the code is making a request that the server doesn't recognise.

    Do you have a complex set of tasks (comments, attachments, subtasks?), or are they fairly basic? I wonder if there's something I've missed that's not being transferred correctly.

    Mike.

  2. Rico S. reporter

    I tried it with different projects most of them are not complex. They only have sometimes a description und sometimes comments.

    I created a project inside Personal Projects called Test and added one task called Test and assigned it to myself and I got the same error. Could it be that the Personal Projects workspace is a little different then the other workspaces?

  3. Mike Houston repo owner

    I don't think it should be any different, I'm able to copy projects of my own to/from/within the personal projects workspace.

    Can you go here: http://asana.kothar.net/?debug=1 and try your test again, then message me with the debug log? Maybe it will reveal something. Otherwise I've no idea what to try I'm afraid.

  4. Mike Houston repo owner

    Thanks Rico,

    Sorry, I'm a bit stumped - I can't see any reason why it wouldn't work. If it's created the project fine, I don't know of any reason why the task creation would fail. My own tests have all worked as expected, including reproducing your test with the same workspace name, etc.

  5. Mike Houston repo owner

    Hi Rico,

    Is the target workspace an Organisation? After another comment, it seems that the new Organisation feature is causing this error message, as the new project needs to be assigned to a team. If it's not an organisation, then this is still a different bug.

  6. Mike Houston repo owner

    Organisation support is now implemented if you feel like retrying the copy. I appreciate it may be a moot point at this stage.

  7. Rico S. reporter

    Hi Mike

    Sorry for my delay. The problem is fixed as far as I can see. I could transfer my projects. Thanks. :-)

  8. Log in to comment