Question

Sync Asana task with Github issues (avoiding an Asana bug)

  • 2 March 2022
  • 2 replies
  • 106 views

For my project, I have 2 Asana plans (A & B) and 5 GitHub repositories (1 to 5).

I want that, 

  • Whenever a task is created from one of the Asana plans (with a custom field indicating the destination repository), an issue is created in the right GitHub repository (with the Asana plan as a label), adding the Asana task link to the body of the GitHub issue.
  • When an issue is created in GitHub in one of the repos, the source Asana task is found in their plan, adding the GitHub issue link as a story (=comment) to this Asana task.

I have managed to do this flow using tags, which is working, but not as expected:

  1. My zap looks for new tag in tasks in asana projects, and if it finds one, a github issue is created with task link. (Then, another zap looks for new github issues and create a comment in the appropriate task with issue link)
  1. It works, but it triggers itself even if I add a custom field info to a task. Thus, it duplicates the github issue (and the comment in asana task).

The problem is that the trigger of “tag added to task in asana” is bugged. I had confirmation from zapier support that it is an Asana bug. In brief, almost any task update triggers the “tag added”, even though it is editing the due date, an assignee, or a custom field…

I can’t directly use the “task created in Asana” due to how Asana works, see my older post.

 

I am sure other teams have been syncing Asana and GitHub in the past

Any creative way of solving this?

cheers :)


This post has been closed for comments. Please create a new post if you need help or have a question about this topic.

2 replies

Userlevel 7
Badge +11

Hey there @Louis MSF!

It sounds like what you need here is a way of checking to see if the task that’s triggering the Zap has been seen previously, when the tag was first added. There’s an article in Community that talks about how to prevent duplicate triggers which you may find helpful in preventing duplicate GitHub issues from being created:


Hope that helps! :slight_smile:   

Hello @SamB and thank you for taking the time to reply.

Indeed that could solve part of the issue. Problem is, sometimes 1 task (Asana) can have multiple tags for multiple repositories (GitHub). Filtering this way would prevent this possibility to exist (if I’m understanding this well).

Therefore, a choice between this secondary feature and the discomfort of my bug should be made^^

Do you agree?