How to link Backlog with Github to automatically register issues as Github Issues when they are created

Items to Prepare in Advance

‍
・Backlog account, project, and test issues (domain and project ID)
・GitHub account, project (account, owner, repository name)

‍

A test project has been set up.

‍

First, copy the Yoom template to My Project. The prefix [Copy] will appear in the template name, but you can change it as desired, so proceed with it as is for now.

The newly copied flow bot has its trigger switch set to [OFF].

As the app integration settings progress, you can switch it to [ON], so let's proceed with it set to [OFF] initially.

‍

First, integrate Yoom with Backlog. Set up the account you prepared in advance.

Next, proceed to project integration.

Set up the integration account and actions. Actions are set to the default template.

‍

‍

The default trigger interval is set to 5 minutes, but you can increase the interval.

‍
Set the domain and project ID.
Domain → Enter the string in the Backlog URL "https://(here)/"
Project → Enter the string in the URL of the issue list page "projectId=(here)"

Press the test button just below.
Test → Success

‍

Next, proceed to the GitHub integration settings. Similarly, set up the integration account for GitHub and proceed to the API connection settings.

Set up the action. The default template is set to "Create Issue", so you can proceed as is.

Select the account to integrate.

Log in with the registered email address and password, but since it is two-factor authentication, please proceed in an environment where you can check your email.

‍

‍

Proceed to the API settings. Here, set the owner name and repository name.

Proceed to test → Success

If it fails, error items will be displayed. The error message is in English, but please use translation to identify the cause.

‍

Once the integration is successful, try starting the flow bot! Turn the trigger [ON] and add an issue to Backlog.

Then, the issue content will be reflected in the GitHub Issue.

‍

‍

I tried several times until I succeeded, but I got an error when I entered the name of the person in charge when setting the issue. This error occurred because the account names were not linked in both Backlog and GitHub.

It can be resolved by performing data mapping, but that is for another occasion.

Add a Task to Backlog When an Issue is Created on GitHub

Conversely, let's integrate a flow bot that reflects the content added to a GitHub Issue in a Backlog task. We will use this template.

The items to prepare in advance are the same as before.

Basically, the order is just reversed from the previous integration, so it was done quickly.

‍

Trigger settings.

We will proceed with the default settings this time as well.

The trigger action is set to "When an issue is newly created" by default, so please proceed to the next step as it is.

Proceed to the API settings of the app trigger. As before, obtain and enter the owner name and repository name.

‍

‍

Once you have entered up to the repository, test it.

‍

Next, proceed to the Backlog settings. Here, you will set the output content for creating tasks.

First, set up the account to be linked. This time, we tested with the same project as the previous integration.

‍

Next, set the output content.

There are many operations to choose from, but let's proceed with the default "Add Task".

‍

Decide on the details of the content to be output to the task.

It would be nice to have certain rules like the start date of the task, but if the timing to start differs for each task, you might need to operate Backlog directly.

If the test is successful, let's activate it.

‍

Turn the Flowbot trigger [ON].

Turn the Flowbot trigger [ON] and activate it! Register a comment on the GitHub Issue.

Since we tested with the same project as before, the tasks added to Backlog and the comments on the Issue went into an infinite loop. The tasks keep increasing endlessly!!

‍

‍

I was a bit surprised, but it seems this can be resolved by setting data mapping in between.‍

We confirmed that a task was created in Backlog from the comment on the Issue, so the integration was a great success!

‍

Other Examples of Automation Using Backlog

There are many other examples of automation using Backlog on Yoom, so let me introduce a few.

1. In this flow, when a task is added to Backlog, a folder is automatically created in Box. This automatically creates a storage location for information to solve the task, eliminating routine work.

2. This is the flow for registering project information in Mazrica when a task is added to the Backlog. By automatically registering information, the speed of information sharing can be increased, leading to quicker responses and decision-making.

3. You can also automate the notification of task registration to LINE WORKS. By automating notifications, you can quickly learn about the addition of tasks and respond promptly to problem-solving.

Summary

This time, by using the template, we were able to achieve app integration according to the default settings.
With this automation, the unification of information between Backlog and GitHub and the speed of information sharing have increased, which is expected to improve work efficiency.

Yoom offers many other flow bot templates, so if you find any templates that interest you, please give them a try!

See you again~!

3.GitHubでプルリクエストが作成されたら、Notionにも追加するという使い方もできます。Notionをデータベースのように使いたい方におすすめです。

BacklogとGitHubを連携することでどのようなメリットがあるか

(1)GitHubからBacklogへ連絡事項・指示内容の通達が自動化できると、状況把握時間の短縮につながります。また、転記ミスがなくなるため確認事項のやりとりも少なくなるでしょう。

(2)共同作業者がどちらかにしか閲覧権限がない場合があります。GitHubは開発者・進行管理担当者以外は権限が限定されていることがあります。そのため、内容の転記までタイムラグが発生しがちです。通達事項の行き来を自動化を行うことで、GitHubの閲覧権限がないメンバーも、プロジェクト全体の状況を把握しやすくなります。

Backlogでは、プロジェクトごとにGitとの連携が可能です。
作業後にプッシュを行うと、課題にコメントで変更点のログを自動で残してくれます。これにより、共同作業する人は更新されたことにいち早く気づくことができるでしょう。
デフォルトではこういった機能が充実していますが、さらに連携を充実させることで課題進行の手間が省けます。

まとめ

今回テンプレートを使って、デフォルトの設定通りにアプリ連携を実現できました。
この自動化により、BacklogとGitHubの情報統一化や情報共有スピードが上がり、業務効率の向上が期待できそうですね。
YoomではBacklog×GitHubだけでなく、その他多数のフローボットテンプレートもあるので、気になったテンプレートがあればぜひ使ってみてください！
では、また〜！