How to centralize GitHub issues and Jira tasks in one to-do list: the best to-do list for freelancers with agile projects

As a freelance developer, juggling multiple GitHub repositories and Jira projects is part of the job. Each client, sprint, and issue competes for your attention, and switching between tools to check what’s pending becomes a time drain. The best to-do list for freelancers with GitHub and Jira projects isn’t one that manages a single project—it’s one that lets you see everything in one place without losing track of each client’s context. Here’s how to achieve that, step by step, with real examples from your daily workflow.

The problem with managing issues in separate tools

Imagine you have three clients today: one uses GitHub for an open-source project, another manages sprints in Jira Cloud, and the third sends issues via email. Every morning, you open three tabs, check notifications, manually copy tasks to a spreadsheet or a generic app like Google Tasks, and by the end of the day, you realize you forgot to prioritize an urgent pull request or respond to a comment in Jira. This isn’t a personal failure—it’s a symptom of a system not designed for freelancers working on multiple agile projects at once.

What you lose by not centralizing your issues

• Context: Every issue in GitHub or Jira contains key information (assignments, deadlines, comments, labels) that gets lost when manually copied to another tool.
• Prioritization: Without seeing all your tasks together, it’s hard to decide what to tackle first when you have a critical bug in one repository and a pending review in another.
• Tracking: You forget to update the status of an issue in the original tool after completing it, which creates confusion with clients or teams.
• Collaboration: If you work with other developers or PMs, you can’t assign them tasks directly from your centralized list, slowing down communication.

How to centralize GitHub and Jira in one to-do list

The solution isn’t migrating everything to a single tool (GitHub and Jira aren’t designed to manage multiple client projects), but automatically bringing your issues into a space where you can organize them as tasks. Here’s how it works in practice:

1. Connect your GitHub and Jira accounts to Foco

Foco integrates with GitHub and Jira via OAuth, meaning you don’t need to share passwords or set up complex webhooks. When connecting each account, you choose a destination workspace for the issues it pulls in: it can be a specific workspace (e.g., "Client X - Backend") or let the AI decide automatically based on the issue’s content. For example, if a GitHub issue has the label "frontend," Foco will assign it to the workspace "Client Y - Frontend."

2. Your issues appear as tasks with full context

Every issue assigned to you or where you’re mentioned in GitHub or Jira is automatically created as a task in Foco, with these fields populated:

• Title: The same as the issue (e.g., "Fix login button not responding").
• Do date: If the issue has a due date in Jira or a milestone in GitHub, Foco uses it as the do date (when you should start working on it).
• Due date: The issue’s deadline, separate from the do date.
• Priority: If the issue is urgent or important, Foco marks it with the corresponding level (based on labels like "high priority" or "blocker").
• Tags: The same labels as the issue (e.g., "bug", "enhancement"), which you can later use to filter tasks.
• Attached notes: A direct link to the original issue, along with the first comment or description. If the issue updates in GitHub/Jira, Foco won’t modify the task, but you can manually refresh it to see changes.

3. Organize your tasks by client or project

In Foco, each workspace is an independent container with its own color. For example:

• Create a workspace called "Client A - API" (blue) for issues from their GitHub repository.
• Create another called "Client B - Sprint 12" (green) for their Jira issues.
• Use Overview mode to see all your tasks together, each with its workspace’s color, so you can quickly identify which client needs attention.

If you need to focus on a single project, switch to Focus mode (by clicking on the workspace) and the dashboard will filter to show only that client’s tasks. This is useful when you’re in a coding session and don’t want distractions from other projects.

4. Complete tasks and sync with the source

When you finish an issue, mark the task as Done in Foco. If you’ve enabled the "complete in source" option, Foco will automatically close the issue in GitHub or add a comment in Jira (e.g., "Resolved in Foco"). This saves you from manually updating each tool, reducing errors and saving time.

Advantages over generic alternatives

Most task apps are designed to manage a single project or for personal use. If you try to use them for multiple clients, you’ll run into limitations like:

• Note-taking apps (Notion, Obsidian): They’re not optimized for tasks with dates, priorities, or automatic sync with external tools. Manually copying each issue is tedious and error-prone.
• Spreadsheets (Google Sheets, Excel): You can create columns for client, priority, or date, but there are no reminders, calendar views, or native integrations with GitHub/Jira. They also don’t scale well when you have hundreds of issues.
• Project managers (Trello, ClickUp): While they allow creating boards per client, they don’t automatically pull in your GitHub/Jira issues. They require complex integrations or Zapier, adding maintenance layers.
• Simple lists (Google Tasks, Apple Reminders): They lack workspace colors, calendar views, or advanced fields like do date vs. due date. They’re useful for personal tasks but not for managing multiple agile projects.

Foco, on the other hand, is specifically designed for freelancers and small teams working on multiple projects at once. Its key advantages are:

• Centralization without duplication: Automatically pulls in your GitHub and Jira issues without manual copying.
• Visual context: Colors by workspace help you quickly identify which client each task belongs to, even in Overview mode.
• Flexibility: See all your tasks together or filter by a single project, depending on whether you need focus or a global perspective.
• Bidirectional sync: Completing a task in Foco updates the original issue in GitHub/Jira, avoiding inconsistencies.
• Developer-friendly views: Kanban mode is ideal for managing sprints, and the calendar shows your issues alongside meetings or deadlines from other projects.

Practical example: a day in the life of a freelancer using Foco

It’s 9:00 AM. You open Foco and see in Overview mode that you have:

• A blue task (Client A - GitHub): "Review PR #42" with urgent priority and a do date of today.
• A green task (Client B - Jira): "Fix API timeout error" with a due date of tomorrow.
• A red task (Client C - Email): "Send architecture proposal" (created by forwarding an email to your Foco capture address).

You decide to start with Client A’s PR. You switch to Focus mode for that workspace and see only its tasks. You use the Kanban view to move the PR to the "Doing" column. At 11:00 AM, you get a Slack notification from Client B: there’s a new issue in Jira. Foco automatically pulls it into your list, with the tag "bug" and high priority. You drag it to the "This week" column in Kanban view. At 3:00 PM, you check the calendar and see that tomorrow you have a meeting with Client C at 10:00 AM, right after Client B’s issue is due. You adjust the do date for the issue to today and block 2 hours in your calendar to finish it. By the end of the day, you mark the PR and issue tasks as done. Foco automatically closes the PR in GitHub and adds a comment in Jira. Your list is updated, and tomorrow you’ll start with Client C’s work.

The best to-do list for freelancers with GitHub and Jira projects isn’t the one with the most features—it’s the one that lets you see everything in one place without losing each client’s context.

Steps to get started today

• Create your workspaces in Foco: One for each client or project (e.g., "Client X - GitHub", "Client Y - Jira"). Assign a different color to each.
• Connect GitHub and Jira: Go to Settings > Connections and add your accounts. Choose whether you want issues to go to a fixed workspace or let the AI distribute them automatically.
• Enable bidirectional sync: In each connection’s settings, check the "complete in source" option so that closing a task in Foco updates the original issue.
• Review your tasks in Overview mode: Use filters by do date or due date to prioritize what’s urgent.
• Try the views: Use Kanban for sprints, List for pending tasks by date, and Calendar to plan your week.
• Set reminders: For issues with due dates, add a reminder 1 day before to avoid surprises.

Centralizing your GitHub and Jira issues in one to-do list isn’t about adding another tool to your workflow—it’s about removing the friction of switching between platforms. With Foco, every issue has its place, every client has its color, and every task has its context. That way, you can focus on what really matters: writing code, solving problems, and delivering quality work without getting lost in management.