How to link Backlog with Github to automatically register issues as Github Issues when they are created
How to Integrate Applications
・
2024/07/01
How to link Backlog with Github to automatically register issues as Github Issues when they are created
k.hieda
Backlog is one of my favorite tools.
The Gantt chart feature is convenient because it visualizes deadlines for each task within a project, making it easy to determine whether things are on schedule. This time, I will introduce efficiency improvements by combining Backlog with GitHub.
What are the benefits of integrating Backlog with GitHub?
In Backlog, you can integrate with Git for each project.
After pushing changes, it automatically logs the changes as comments on the tasks. This allows collaborators to quickly notice updates.
These features are well-equipped by default, but enhancing the integration can further reduce the effort required for task progress.
Trying out the integration of Backlog and GitHub using Yoom
(1) Automating the communication of notices and instructions from GitHub to Backlog can shorten the time needed to understand the situation. Additionally, it reduces the chances of transcription errors, leading to fewer exchanges of confirmation details.
(2) There may be cases where collaborators only have viewing permissions on one platform. GitHub often restricts permissions for those who are not developers or project managers. As a result, there tends to be a time lag until the content is transcribed. By automating the exchange of notices, even members without GitHub viewing permissions can easily grasp the overall project situation.
(3) With Yoom, you can integrate not only Backlog and GitHub but also other apps and workflows. By further automating tasks, you can reduce errors and secure thinking time to increase productivity.
"I don't think being able to see both sets of instructions will significantly improve work efficiency."
That's right! The transcription work between Backlog and GitHub itself is not a difficult task.
However, when there are many projects, just going back and forth between the two apps consumes quite a bit of time. By securing thinking time to increase productivity as mentioned in point ③, and by allowing ample time for operation checks, you might be able to aim for quality improvement.
First, let's try the flow where tasks registered in Backlog are transcribed to GitHub Issues! We will use this template.
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~!
The person who wrote this article
k.hieda
10 years as a web planner and director. When I worked for a web production company, my main focus was on proposing modifications and operation plans to clients and proceeding with production. I'm currently a parallel worker. We produce blogs in Yoom's content division, and receive external public relations projects for companies in our individual business. Since we are starting a private lodging, we aim to thoroughly improve the efficiency of routine work!
Conventional RPA can only automate simple repetitive tasks, and the setup process was very complicated. With “hyperautomation,” which combines various technologies such as AI, API, RPA, and OCR, it is possible to automate many tasks that could not be realized until now more easily than before.
Most tools simply connect one app to another, leaving the complex tasks to you. Yoom goes much further: From document creation and browser automation to OCR and generative AI, Yoom handles it all seamlessly in one platform.
Why settle for basic integrations? Streamline your entire workflow with Yoom’s powerful hyperautomation.