How to Consolidate Tasks from Notion, Linear, GitHub, Jira, and Asana into One Time Block

If you manage tasks across Notion, Linear, GitHub, Jira, and Asana, you lose 20-40 minutes daily switching between tools—time spent reorienting, checking for updates, and manually syncing progress. Foco Plus eliminates this by pulling tasks from all these apps into one dashboard, where you can process them in a single time block. Here’s how it works and why it’s different from traditional tools.

How Foco Plus Pulls Tasks from Multiple Apps (Exact Mechanism)

Foco Plus connects to Notion, Linear, GitHub, Jira, and Asana via OAuth. When you enable a connection, Foco automatically imports tasks where you’re assigned or mentioned. Each task arrives with:

• Source metadata: The original app’s name (e.g., "GitHub") and a link back to the item.
• Context: A "destination work" in Foco, either chosen by you (e.g., "Client X") or auto-assigned by Foco’s AI based on content (e.g., a GitHub issue tagged backend goes to the "Development" work).
• Fields preserved: Title, due date, assignee, and status (e.g., "To Do").
• Option to complete in origin: When you mark a task as done in Foco, it closes or comments on the original item in the source tool (e.g., a GitHub issue moves to "Closed"). This keeps both tools in sync without manual updates.

Example: How a GitHub Issue Appears in Foco

A GitHub issue titled "Fix login API bug" with a due date of June 10 and labeled urgent arrives in Foco as:

• Work: "Development" (auto-assigned by AI or manually set).
• Title: "Fix login API bug".
• Due date: June 10 (appears in Calendar view).
• Priority: Urgent (color-coded in List view).
• Source: GitHub (with a direct link to the issue).
• Option to complete in GitHub: Enabled by default; marking it done in Foco closes the issue in GitHub.

Step-by-Step: How to Group Tasks into a Single Time Block

Step 1: Set Up Connections (Takes <5 Minutes)

1. Go to Settings > Connections in Foco Plus and select the app (e.g., GitHub).

2. Authenticate via OAuth. Foco requests minimal permissions (e.g., read/write access to issues assigned to you).

3. Choose a destination work for the connection:

• Fixed work: All tasks from GitHub go to "Development".
• Automatic (AI): Foco assigns tasks based on content (e.g., a GitHub issue with frontend in the title goes to "Web App").

4. Enable "Complete also in origin" to sync progress back to the source tool.

Step 2: Use Panorama Mode to See All Tasks at Once

In Panorama mode, Foco shows tasks from all works (e.g., "Development," "Clients," "Home"), each with its work’s color. Example:

• Blue tasks: Development (GitHub, Jira, Linear).
• Green tasks: Design (Notion).
• Gray tasks: Personal (Notion, manual entries).

This lets you spot overlaps or priorities across tools. For example, if a Jira issue (blue) and an Asana task (green) are both due today, you can decide which to tackle first.

Step 3: Create Time Blocks by Work Type

Assign fixed time slots to process tasks from one work at a time. Example schedule for a freelance developer:

• 9:00-10:00: Development Block. Enter Foco mode for the "Development" work. Filter tasks from GitHub, Jira, and Linear. Use Kanban view to drag issues between columns (e.g., "To Do," "In Progress," "Review"). On mobile, tap tabs to switch columns.
• 10:30-11:30: Client Block. Switch to the "Clients" work. Filter Asana and Notion tasks. Use List view to group by due date (e.g., "Today," "This Week") or priority (urgent/important).
• 12:00-12:30: Personal Block. Switch to the "Home" work. Use Calendar view to assign tasks like "Pay rent" to a specific day.

Step 4: Use Foco’s Views to Adapt to Each Block

Switch views with the Vista button to match your workflow:

• List view: For quick reviews. Groups tasks by date (Today, This Week, Later) or priority. Example: In the "Clients" block, filter by "urgent" to see only tasks due today.
• Kanban view: For execution. Drag tasks between columns (e.g., "To Do" → "In Progress"). On desktop, drag-and-drop; on mobile, tap tabs to switch columns.
• Calendar view: For planning. Assign start dates to tasks and visualize them alongside Google Calendar/Outlook events. Example: Reserve Tuesday for design tasks and Thursday for development.

Real Example: A Day Using Foco Plus for Time Blocking

Scenario: You’re a freelance developer with three clients:

• Client A: Uses Jira for bugs and Linear for features.
• Client B: Uses Asana for tasks and Notion for docs.
• Client C: Uses GitHub for issues.

8:30 AM: Open Foco’s daily briefing (Plus plan). It shows:

• A Jira issue due today ("Fix login API bug").
• An Asana task for Client B ("Review wireframes") due tomorrow.
• A GitHub PR review requested by Client C.
• Calendar: Meeting with Client B at 11:00 AM.

9:00-10:30 AM: Development Block

• Enter Foco mode for "Client A."
• Filter tasks from Jira and Linear. Use Kanban view to move the Jira issue to "In Progress."
• Add a note with a screenshot of the bug. Mark it as "urgent."

10:30-11:00 AM: Client Block

• Switch to "Client B."
• Filter Asana tasks. Use List view to group by due date. Reschedule the wireframe review to tomorrow.
• Use Ráfaga to dictate: "Follow up with Client B on wireframe feedback. Due Friday." Foco creates the task with the due date and priority.

11:00-12:00 PM: Meeting with Client B

• Use listen mode to record the meeting. Foco transcribes it and saves the audio as a note.
• After the meeting, use Ráfaga to create tasks from the transcription (e.g., "Update wireframes per feedback. Due Thursday. Important.").

4:00-5:00 PM: Follow-Up Block

• Use Panorama mode to review all tasks with reminders or due dates today.
• Mark the Jira issue as done. Foco closes it in Jira automatically (if "Complete also in origin" is enabled).
• Reschedule the GitHub PR review to tomorrow.

Why Foco Wins Over Traditional Tools for Multiple Jobs

1. No per-user costs. Foco’s collaboration is free (unlike Asana’s Starter plan, which costs $10.99/user/month and requires a minimum of 2 seats).

2. Visual separation of jobs. Each work has a color, and tasks inherit it. In Asana or Notion, you’d need to manually set up labels or projects to achieve this.

3. Automatic task imports. Foco pulls tasks from Notion, Linear, GitHub, Jira, and Asana without manual integrations (unlike Asana, which requires Zapier or its API).

4. Voice capture and Ráfaga. Dictate tasks faster than typing. Ráfaga separates multiple tasks from one dictation (e.g., "Call Client A about invoice. Review GitHub PR. Pay rent. Due tomorrow.").

5. Daily briefing. Foco Plus generates a summary of what’s due, what needs attention, and calendar updates (unlike Asana, where you’d need to manually review each project).

When to use alternatives: If you manage a large team with advanced needs (e.g., workload management), Asana or ClickUp might fit better. But for freelancers or solopreneurs, Foco’s simplicity and cost make it the better choice.

Key Decisions When Setting Up Foco Plus

1. Fixed Work vs. Automatic Assignment

Fixed work: All tasks from GitHub go to "Development." Best if you want consistency (e.g., all development tasks in one place).

Automatic (AI): Foco assigns tasks based on content. Best if your tools have clear labels (e.g., frontend, backend). Example: A GitHub issue labeled frontend goes to "Web App," while backend goes to "API."

2. Enabling "Complete Also in Origin"

Pros: Syncs progress back to the source tool (e.g., closing a GitHub issue when marked done in Foco).

Cons: Requires write permissions. If you’re not the owner of the source tool (e.g., a client’s Jira), you may not have access.

3. Choosing Between List, Kanban, and Calendar Views

List view: Best for reviewing tasks by date or priority (e.g., "What’s due today?").

Kanban view: Best for execution (e.g., moving tasks between "To Do" and "In Progress").

Calendar view: Best for planning (e.g., assigning tasks to specific days).

Common Mistakes to Avoid

• Overloading a single work. Example: Putting all GitHub, Jira, and Linear tasks into one "Development" work. Instead, create separate works (e.g., "Client A Dev," "Client B Dev") to avoid mixing contexts.
• Not using Panorama mode. Without it, you’ll miss tasks from other works. Example: A personal task (e.g., "Pay rent") might get buried if you only check the "Clients" work.
• Ignoring the daily briefing. It surfaces tasks you might overlook (e.g., a Jira issue due today). Set it to arrive at a fixed time (e.g., 8:30 AM).

How This Compares to Other Methods

Bullet Journal for Multiple Jobs: Exact System to Separate Contexts Without Losing the Big Picture explains how to separate jobs manually, but it requires constant upkeep. Foco automates this by pulling tasks from tools and color-coding them.

How to Unify Tasks from Multiple Apps in One Place Without Migrating Data: A Practical Guide with Foco Plus dives deeper into Foco’s connections, including how to handle edge cases (e.g., tasks with no due date).

Time Blocking for Multiple Clients: Exact System to Avoid Overlaps and Double Bookings covers how to schedule time blocks without conflicts, including how to use Foco’s Calendar view to avoid double-booking.

The goal isn’t to do more tasks—it’s to do the right tasks at the right time, without wasting time switching between tools or manually syncing progress.

FAQ

Does Foco Plus work with tools not listed (e.g., Trello, ClickUp)?

Foco Plus currently supports Notion, Linear, GitHub, Jira, Asana, and MCP servers. For unsupported tools, you can manually add tasks or use Foco’s email capture (u-xxxx@in.heyfoco.com) to forward tasks as emails.

What happens if a task is updated in the source tool (e.g., GitHub) after it’s imported to Foco?

Foco doesn’t auto-sync updates from the source tool. You’d need to manually refresh the connection or re-import the task. However, if you mark a task as done in Foco and have "Complete also in origin" enabled, it updates the source tool.

Can I assign tasks to team members in Foco?

Yes, but only to people you’ve invited to a work. Example: Invite a client to the "Client A" work and assign them a task. They’ll see only that work, not your other tasks.

How does Foco handle recurring tasks from source tools (e.g., a weekly Jira issue)?

Foco imports the task once. If it’s recurring in the source tool, you’ll need to manually set up recurrence in Foco or re-import the task when it reappears in the source tool.

Is there a limit to how many tasks Foco can import?

No. Foco imports all tasks where you’re assigned or mentioned, with no cap on the number of tasks or works.