How to Unify Tasks from GitHub, Jira, Asana & More in One Dashboard Without Migrating Data

To unify tasks from GitHub, Jira, Asana, Linear, or Notion in one dashboard without switching tools, use Foco Plus Connections. This feature imports tasks from these platforms into Foco via OAuth, displaying them alongside your other work in a single interface. Tasks retain their original metadata (due dates, priorities, assignees) and update automatically when you mark them as done in Foco (if bidirectional sync is enabled). Here’s how it works:

• Automatic import: Tasks appear in Foco within minutes of being assigned to you in the original tool, with no manual copying.
• Context-aware routing: Each task is assigned to a 'work' (e.g., 'Frontend Dev' or 'Client X') based on its content or a fixed rule you set. For example, a GitHub issue labeled 'backend' goes to the 'API Development' work, while a Jira ticket with the project 'Support' goes to 'Customer Service'.
• Bidirectional sync (optional): Marking a task as done in Foco closes it in GitHub (as a closed issue), resolves it in Jira, or completes it in Asana, eliminating duplicate updates.
• Filters to reduce noise: Exclude tasks by status, labels, or due dates. For example, import only GitHub issues assigned to you or Jira tickets with a due date in the next 7 days.
• Unified views: See all tasks in Panorama mode (color-coded by work), or switch to Kanban or Calendar to plan your week. Filter by priority, due date, or work to focus on what matters.

Step-by-Step Setup for Foco Plus Connections

1. Connect your tools via OAuth

Go to Settings > Connections in Foco (desktop or mobile) and select the tool you want to connect (GitHub, Jira, Asana, Linear, or Notion). Authenticate with your account—no credentials are stored in Foco. This requires the Plus plan (20 €/month).

2. Choose where tasks appear

For each connection, decide where imported tasks should go:

• Automatic (default): Foco analyzes the task content (title, labels, project) and assigns it to the most relevant work. For example, a GitHub issue with the label 'frontend' goes to the 'Frontend Dev' work, while a Jira ticket with the project 'Marketing' goes to 'Client Campaigns'.
• Fixed work: All tasks from a connection go to the same work. Useful if all your GitHub issues belong to one project (e.g., 'Mobile App'). Change this anytime in Settings > Connections > [Tool] > Edit.

3. Enable bidirectional sync (optional)

By default, Foco imports tasks but doesn’t modify them at the source. Enable 'Complete also in the source' to close issues, resolve tickets, or complete tasks in the original tool when you mark them as done in Foco. This works for GitHub (issues/PRs), Jira (tickets), Asana (tasks), Linear (issues), and Notion (tasks).

Bidirectional sync isn’t instant: tasks update in the original tool within 1-2 minutes to avoid API rate limits.

4. Set filters to avoid irrelevant tasks

In Settings > Connections > [Tool] > Filters, define which tasks to import. Examples:

• GitHub: Import only issues assigned to you or pull requests where you’re a reviewer. Exclude issues with labels like 'wontfix' or 'documentation'.
• Jira: Import only tickets with status 'In Progress' or 'To Do', and exclude those in the 'Backlog' or with labels like 'low-priority'.
• Asana: Import only tasks with a due date in the next 14 days or with the 'high-priority' tag.

Real Workflows for Developers and Teams

Workflow 1: Full-stack developer with GitHub and Jira

A developer working on a frontend (GitHub) and backend (Jira) team can:

• Connect GitHub and Jira, assigning GitHub issues to the 'Frontend' work (blue) and Jira tickets to the 'Backend' work (green).
• Use Panorama mode to see all tasks in one list, color-coded by work. Filter by 'urgent' priority to focus on critical items.
• Mark a task as done in Foco’s Kanban view, and it closes automatically in GitHub or Jira. No need to switch apps.
• Use voice capture to add tasks: dictate 'Review PR #456 for frontend by tomorrow 2 PM', and Foco creates the task with the correct date, time, and work.

Workflow 2: Technical team with Asana and GitHub

A team using Asana for project management and GitHub for code can:

• Connect both tools, assigning Asana tasks to the 'Management' work and GitHub issues to the 'Development' work.
• Use the Calendar view to block time for GitHub PR reviews and Asana milestones in the same schedule. Avoid overlaps by dragging tasks to available slots.
• Share a task link with a teammate (e.g., a GitHub issue) without giving them access to the rest of Foco. They see only that task via a public link.
• Use Ráfaga to capture multiple tasks at once: dictate 'Fix login bug in GitHub, update docs in Asana by Friday, sync with backend team', and Foco splits it into three tasks with the correct works and due dates.

What Foco Does (and Doesn’t Do) with Imported Tasks

Foco acts as a read-only layer for tasks from GitHub, Jira, Asana, etc. Here’s what you can and can’t do:

• ✓ What you can do: View tasks from all tools in one dashboard, filter by priority/due date/work, mark tasks as done (with optional bidirectional sync), add notes/labels/reminders to imported tasks, and share task links with teammates.
• ✗ What you can’t do: Edit task titles, descriptions, or assignees in the original tool from Foco. Create new tasks in GitHub/Jira/Asana from Foco. Sync tasks in real time (updates occur every few minutes).

Why Foco Wins Over Spreadsheets, Notion, or Generic Project Managers

Alternatives to unifying tasks from multiple apps fall short for technical workflows:

• Spreadsheets (Google Sheets, Excel): Manual copying is error-prone and time-consuming. No automatic sync, no Kanban/Calendar views, and no way to update statuses in the original tool. Example: A developer would need to manually update a spreadsheet every time a GitHub issue changes status, adding 10+ minutes of overhead per day.
• Notion/Obsidian: Requires manual setup for each tool. No native integrations with GitHub/Jira, so you’d need to use APIs or third-party plugins. Example: To import GitHub issues into Notion, you’d need to set up a custom automation with Zapier or Make, which breaks when GitHub’s API changes.
• Generic project managers (Trello, ClickUp): Designed for single projects, not technical tools. Lack deep integrations with GitHub/Jira and often force you to adapt to their workflow. Example: ClickUp’s GitHub integration is limited to basic issue imports and doesn’t support bidirectional sync for status updates.

Foco is built for people who manage multiple jobs at once and need a lightweight layer on top of existing tools. It doesn’t replace GitHub, Jira, or Asana—it unifies them so you can see everything in one place, prioritize effectively, and avoid context-switching. For example, a developer can review GitHub PRs, update Jira tickets, and check Asana milestones in Foco’s Panorama mode, saving 30-60 minutes per day in app-switching.

How to Start: A 15-Minute Setup

Follow these steps to unify your tasks in Foco today:

• Activate the Plus plan (20 €/month) in Foco and go to Settings > Connections.
• Connect one tool first (e.g., GitHub). Set the 'destination work' to Automatic to see how Foco routes tasks.
• In Panorama mode, filter tasks by 'urgent' priority or due date to focus on what’s critical. Use Critical Power List: How to Identify, Prioritize, and Execute Critical Tasks (Exact Steps for Freelancers) for prioritization techniques.
• Enable bidirectional sync for the tool you connected. Test it by marking a task as done in Foco and verifying it updates in the original tool.
• Add a second connection (e.g., Jira or Asana) and repeat the process. Use filters to exclude irrelevant tasks (e.g., Jira tickets in 'Backlog').
• For teams, invite colleagues to Foco and assign tasks to them. Use the Kanban view to track progress across tools. Learn how to avoid overlaps with Time blocking for freelancers with multiple clients: how to avoid overlaps and boost productivity.

Start with one tool and refine your filters until only relevant tasks appear. Once set up, Foco reduces app-switching by 70-90%, based on user feedback from developers and technical teams.

How This Fits Into Your Existing Workflow

Foco doesn’t replace your tools—it enhances them by giving you a unified view. Example workflows:

• Morning: Open Foco’s Panorama mode to see all tasks from GitHub, Jira, and Asana. Filter by 'urgent' and 'due today' to plan your day. Use Parkinson's Law for managing multiple jobs and avoiding procrastination: a practical guide to allocate time blocks.
• During the day: Use voice capture to add tasks on the go. Example: 'Fix API bug in GitHub by 3 PM, review Asana milestone for Client X'. Foco transcribes it and creates two tasks with the correct works and due dates.
• End of day: Mark tasks as done in Foco’s Kanban view. Bidirectional sync updates their status in GitHub/Jira/Asana automatically. Use the Calendar view to review what’s due tomorrow.

For teams, Foco’s collaboration features let you assign tasks to teammates without leaving the app. Example: A tech lead can assign a GitHub issue to a developer in Foco, and the developer sees it in their dashboard with the correct work and priority.

FAQ: Unifying Tasks from Multiple Apps

FAQ

Does Foco create new tasks in GitHub, Jira, or Asana?

No. Foco imports existing tasks from these tools but doesn’t create new ones. You’ll still use GitHub, Jira, or Asana to create tasks, and Foco will import them automatically.

How often does Foco sync with connected tools?

Tasks update every 2-5 minutes to avoid overloading APIs. This isn’t real-time sync, but it’s frequent enough to keep your dashboard current.

Can I edit task details (title, description, assignees) in Foco?

No. Foco is a read-only layer for tasks from GitHub, Jira, etc. You can add notes, labels, or reminders to imported tasks, but you can’t edit their core details. To make changes, open the task in the original tool.

What happens if I disconnect a tool from Foco?

Imported tasks from that tool remain in Foco but won’t update. You can still mark them as done, but bidirectional sync stops working. Reconnecting the tool resumes syncing.

Can I use Foco to unify tasks from tools not listed (e.g., Trello, ClickUp)?

Foco currently supports GitHub, Jira, Asana, Linear, Notion, and MCP servers. For other tools, you’d need to use their APIs or export tasks manually. See How to Unify Tasks from Multiple Apps in One Place Without Migrating Data: A Practical Guide with Foco Plus for alternatives.