How to create an issue on GitHub when a task is added to a specific section in Asana

[What is Yoom]

Now, let's explain how to use the no-code tool Yoom to "add a new task to a specific section in Asana and then add it as an Issue in GitHub".

How to Create an Issue in GitHub When a Task is Added to a Specific Section in Asana

This can be achieved by receiving the addition of a new task in a specific section of Asana via API and automatically adding it as an Issue in GitHub using GitHub's API.
Generally, programming knowledge is required to achieve this, but with the no-code tool Yoom, it can be easily done without programming knowledge.

The general flow is as follows:

• Connect Yoom with Asana and GitHub as My Apps
• Copy the template
• Configure the flow details
• Turn on the trigger

If you are not using Yoom, please register for free here.
If you are already using Yoom, please log in.

Step 1: Connect Asana and GitHub as My Apps

After logging into Yoom, click "New Connection" from the "My Apps" menu on the left.

‍

‍

‍

When the search window appears, enter the app name and search.

Connect Asana as My App

First, sign in to Asana.
Next, grant permissions in Asana.

Then return to Yoom, and the My App connection is complete.

‍

‍

Connect GitHub as My App

First, log in to GitHub.

Click "Sign in" to automatically connect with Yoom.
That was easy!

Make sure it is added to My App connections.

‍

‍

Next, proceed to configure the flow details. Click "Try it" from the banner below to copy the template.

Step 2: Set Up App Trigger in Asana

‍

‍

The initial setting is "When a new task is added to a specific section".
The first page reflects the account information of Asana that has completed my app integration.

‍

‍

If necessary, modify the title, check the account information, and proceed to the next step.

On the next page, set the trigger activation interval.

‍

‍

The trigger activation interval can be selected from 5 minutes to 60 minutes.
Please note that it may not be selectable depending on the plan of Yoom's contract.

After selecting other required items from the options, create a new task in Asana and click "Test".

‍

‍

If the content of the newly created task can be obtained in the output, click "Save" to complete the trigger setting.

Step 3: Set Up Issue Creation in GitHub

‍

‍

Next, let's create an Issue in GitHub using the information obtained from Asana.
On the first page, as before, modify the title and check the account information before proceeding.

Next, set the content to be registered as an Issue.

In addition to obtaining the repository name from the list of Issues, you can also check it from "Setting".

Try entering the necessary information for the title and comment while utilizing the output.

‍

‍

Once everything is entered, click "Test".
Since the output is also obtained in Yoom, click "Save" to complete all settings.

Finally, turn on the trigger to activate the flow.

‍

‍

Now, when a task is newly created in Asana, an Issue will be automatically created in GitHub.
The flow you set up is as follows.

To Further Automate

Once you become familiar with operating Yoom, try arranging the flow to make it even more user-friendly.
<span class="mark-yellow">You can change the trigger to an email or utilize branching to create a flow that better suits your work.</span>

Refer to the following to achieve "I wish it could be just a little more like this."

Create Tasks with Email Triggers

For example, what should you do if you want to register requests from outside the company as tasks?
In such cases, try changing to an email trigger.

‍

‍

Using Yoom's email feature, you can set it to "automatically create a task if the subject contains [Inquiry]."
<span class="mark-yellow">This means that responding to inquiries directly becomes a task.</span>

Additionally, you can summarize content from specific senders and reflect it in tasks.

By combining email features with AI, the range of flow utilization seems to expand.

Notify Responsible Persons Using Branching

For tasks with approaching deadlines, you want to notify the responsible person directly to proceed efficiently with the work.

‍

‍

In such cases, try utilizing branching.
You can branch and notify (or send an email to) specific people based on specified conditions.

You can set branching based on deadlines, priorities, or specified keywords, so try arranging it to match your work content!

Note that branching is a feature available in plans above the mini plan. In the free plan, the flow bot you set will result in an error, so please be careful.
Paid plans offer a two-week free trial, during which you can use the branching feature.

Other Automation Examples Using Asana and GitHub

In addition to the flows introduced this time, you can achieve various work automations by utilizing the APIs of Asana and GitHub.
All can be used with simple settings, so if there's anything you're interested in, please give it a try!

Other Automation Examples with Asana and GitHub

This is a flow where a new issue created in GitHub is automatically registered as a task in Asana.

GitHub Automation Example

Add to GitHub When a Task is Registered

When a task is registered, it can be automatically added to GitHub, streamlining management tasks.

Notify When an Issue is Created on GitHub

Automatically notifying when an issue is created on GitHub allows the entire team to smoothly grasp the issue information, enabling prompt responses and discussions.

Add a Task When an Issue is Created on GitHub

By using the referenced information when creating, it might be possible to reduce manual input errors.

Automation Example Using Asana

When a task is added to Asana, add an issue or task

Automatic information reflection reduces manual work, making business processes run more smoothly.

Notify When a Task is Completed in Asana

Automatically send a notification to your communication tool after a task is completed in Asana.

Benefits and Specific Use Cases of Integrating Asana and GitHub

Benefit 1: Centralized Management of Tasks and Development Progress

By integrating Asana and GitHub, task management and code management are seamlessly connected. Tasks created in Asana are registered as GitHub Issues, allowing engineers to easily check "Which task should I work on?" directly on GitHub.

For example, when progressing with the development of a new feature, adding a task like "Implement ○○ feature" in Asana automatically creates an Issue in GitHub. This allows engineers to understand tasks on GitHub without having to check Asana, saving time. Additionally, Asana tasks can be automatically updated when a pull request is created, making it easier for the entire team to share development progress.

Benefit 2: Visualization of Project Progress

Have you ever felt that development progress is hard to see and information sharing within the team is not going well? By integrating Asana and GitHub, task progress is reflected in real-time in Asana, making it easy to see the "current status" of the project at a glance.

For instance, if the marketing team is preparing for the release of a new feature on Asana, integrating with GitHub allows the Asana task to be automatically updated to "completed" when an engineer creates a "development complete" pull request. This means that non-engineering members can easily determine "Is this feature ready for release?" just by looking at Asana, without waiting for progress reports from the development team.

Benefit 3: Smoother Team Collaboration and Reduced Communication Effort

Interactions between different teams, such as development, design, marketing, and project managers, become smoother. There is no need to constantly ask "What is the status of this task?" which reduces unnecessary confirmation work and makes it easier to proceed with tasks efficiently.

For example, when a designer adds a task like "UI modification" in Asana, it is automatically reflected as an Issue in GitHub. Engineers can proceed with their work by checking the Issue on GitHub, eliminating the need for questions like "How far along is this modification?" Furthermore, when an engineer creates a pull request, it is also reflected in Asana, making it easier for designers to check the modification details.

In this way, integrating Asana and GitHub is expected to facilitate smooth information sharing across the entire team, making work easier to proceed.

Conclusion

Integrating Asana and GitHub reduces the hassle of task management and streamlines team operations.
With Yoom, it's attractive that you can easily set up the integration without programming knowledge.

For those who want to eliminate manual input between tools and manage tasks more efficiently, Yoom is the optimal choice.
‍You can start with a 2-week free trial, so register with Yoom first and experience the convenience of automation!