mannieschumpert

@snowfox

This feature isn't included (yet). But I am looking into adding it.

@Jonathan Ray:

After hearing a similar report via Twitter, it was revealed that the Asana API was temporarily out of service.

@V.A.:

I worked on it a bit weekend before last, but there's some real peculiarities to the way Alfred was encoding/decoding JSON, which is why special characters get busted. I haven't found a solution, but Alfred has some new debugging features. Once I find time to explore those, I might be able to find a solution.

@Jonathan

What does "tasks not showing up" mean? Were you adding tasks with QuickTask, and they weren't showing up in the Asana app?

Also, that error is occurring because the Asana API is not returning any workspaces, which means either you don't have workspaces or there is a problem with your API key. The "tasks not showing up" problem would also support the possibility that there is a problem with your key.

That is definitely the reason!

I didn't test for Portuguese when I built it.

I see what is happening now, and probably can figure out a workaround. I'll keep you posted.

Hey V.A.,

That is rather odd, and definitely shouldn't be happening.

Do you get this result no matter which workspace you choose?

What happens if you set the task target to a project with aproject? Will adding a task work then?

Huh, I have actually not seen that particular error message before.

However, please see http://mannieschumpert.com/quicktask/#known-issues

Try escaping the apostrophe. It's annoying, I know, but there doesn't seem to be a way around it. :/

I had some revelations, and probably will add the ability to add tags and description, but only at time of task creation.

Management of existing tasks still will likely never be considered for addition.

@rjfrizz,

This is just my perception, but I think I'm right: there's no way an Alfred workflow can do those things more efficiently than using the Asana web interface.

It would be exceedingly difficult to program, and I believe the results would absolutely not increase productivity. So, I can say with almost 100% certainty that I won't ever even try to add those features. Sorry to disappoint.

I just released a new version that solves @jk02478's problem, as well as adds the ability to create new projects.

Details at my site:

http://mannieschumpert.com/quicktask/

Huh, project names with parentheses is definitely not a use-case I foresaw.

I'll take a look and see if I can sort it out.

In particular, a single, aggregate option to escape the entire query for use in bash would be great.

Yes, please!

As of now, there seems to be no way I can get my workflow for Asana working just right, because there isn't an option to escape single quotes.

Now listed on Asana's apps page!

https://asana.com/apps/alfred

Congrats! You found an edge case!

For some reason, if a task is added to a workspace Asana won't show it unless it is explicitly assigned to you.

(If you set the task target as a project, due dates should work as expected.)

I thought I had covered this quirk, but it looks like I missed it!

Anyway, I updated the download link with the fixed version.

Sweet! the new version works great! Is there a way to over ride what project task goes into using an option? Or do i have to switch it every time? Maybe when i type aproject and press another key (command, right arrow etc) then the task will go into that project?

I'm not sure the functionality you propose is even possible. But you don't have to set the target every time. Once you set the target, you don't have to set it again unless you need to switch projects. It's as it is because generally you will focus on one project for a period of time, and won't need to change back and forth much. In this way, it also encourages focused workflow.

Thanks for the report!

It's fixed. You can download the new version at the same link.

The other idea is a good one, and probably doable. I'll take a look at the possibility for a future update.

You can always run azone again - it will overwrite the previous setting.

If somehow you're stuck at the second step of choosing a zone, just pick any zone, then start the process over.

I've completely re-written the workflow. It's so much better!

Here's a new link to the info page:

http://mannieschumpert.com/quicktask/

I have some new features in the works!

Soon you'll be able to set assignee and due date when creating a task.

Just be sure to follow this thread for updates!

Actually, the amail trigger will do this.

Just run amail and put in your assistant's email (the one registered with Asana), and it'll work! You just have to remember to run it again with your own email to set it back.

I just pushed an update that solves the case sensitivity. (So you can enter lowercase if you want.)  

You'll have to run aget again to refresh the necessary data.

You can re-download from the same link.

Well, it's currently not typo-friendly. It's case-sensitive, so first, make sure you're entering the workspace name exactly as it is named in Asana.

Also, I just need to be sure you're not mixing workspaces and projects. aspace only works to set an existing workspace as the target, and aproject only works to set an existing project as the target.

Updated for projects!

See my blog post for details and download:

http://mannieschumpert.com/blog/alfred-workflow-for-asana/

I'm pretty sure I can extend it to work with projects, and I think I can do so without compromising my goal of quickness.

Stay tuned!

This didn't work for me, either, and I'm not really sure why.

I really wanted a solid workflow for Asana, though, so I created one:

http://www.alfredforum.com/topic/2801-asana-quick-task/

I developed a fairly robust workflow for Asana. Its main purpose is to allow for the fastest possible adding of tasks.

You can read more about it and the instructions for its use on my site:

http://mannieschumpert.com/quicktask/

And you can download the workflow here:

http://bit.ly/1afnipH

There are also instructions in the workflow Readme.

It has fairly comprehensive error handling, but if you find any bugs, please let me know!

Credit to David Ferguson for his workflow PHP class, without which I probably couldn't have pulled this off.