How to See GitHub, Jira, Asana, Notion, and Email Tasks in One Dashboard (Exact Steps)

To consolidate tasks from GitHub, Jira, Asana, Notion, and emails into one dashboard without switching tools or migrating data, follow this exact setup: (1) Connect each app via OAuth in Foco Plus, (2) choose a destination work (automatic or fixed), (3) enable 'Complete also in source' to sync status bidirectionally, and (4) forward emails to your unique u-xxxx@in.heyfoco.com address. Tasks appear in Foco within seconds, with colors for each project, and updates in Foco close the original item in its source tool. No manual copying, no lost context.

Step-by-Step: Connect GitHub, Jira, Asana, and Notion in 5 Minutes

1. Authorize Each Tool via OAuth (No Passwords)

In Foco Plus, go to Settings > Connections. Select GitHub, Jira, Asana, or Notion. You’ll be redirected to the tool’s login page. Authorize Foco to access your assigned tasks (e.g., GitHub issues where you’re mentioned, Jira issues assigned to you). No API keys or passwords are stored in Foco.

2. Choose Where Tasks Appear: Automatic or Fixed Work

For each connection, select a destination work:

• Automatic (AI decides): Foco analyzes the task title, description, and tags to assign it to the correct work. Example: A GitHub issue titled 'Fix login bug for Client X' is automatically assigned to the 'Client X Development' work (if it exists). Use this if you work with 5+ clients or projects.
• Fixed work: All tasks from the connection go to one work. Example: All Asana tasks from 'Marketing Agency' go to the 'Marketing Agency' work. Use this if a single client uses one tool exclusively.

You can change the destination anytime in Settings > Connections. Tasks already synced won’t move, but new ones will follow the updated rule.

3. Filter Which Items Sync (Avoid Noise)

Each integration brings only what’s relevant to you. Default filters:

• GitHub: Issues assigned to you, pull requests where you’re a reviewer, and mentions in comments. Excludes closed issues or PRs you’ve already reviewed.
• Jira: Issues assigned to your user. You can filter by project (e.g., only sync 'Client Y' project).
• Asana: Tasks assigned to you in any project or team. Excludes subtasks unless you’re the assignee.
• Notion: Pages or database items where you’re mentioned or assigned. Supports task lists and databases with 'Assignee' properties.

To adjust filters, go to Settings > Connections > [Tool] > Edit. Example: In Jira, you can exclude issues with the label 'internal' if they’re not relevant to your work.

4. Enable 'Complete Also in Source' (Bidirectional Sync)

Check this box to close or comment on the original item when you mark a task as done in Foco. Examples:

• GitHub: Marking a pull request as done in Foco closes it in GitHub with the comment 'Completed in Foco'.
• Jira: Completing an issue adds a 'Resolved in Foco' comment and changes its status to 'Done'.
• Asana: The task is marked as completed in Asana.

If you disable this, you’ll need to manually update the original tool. Useful if you prefer to review changes first (e.g., for client approval).

How to Add Email Tasks Without Manual Entry

Forward emails to your unique u-xxxx@in.heyfoco.com address (visible in Settings > Email Capture). Foco extracts:

• Task title: The email subject (e.g., 'Review contract draft by Friday').
• Due date: If the email includes 'by Friday' or 'due 2026-07-15', Foco sets the due date automatically.
• Start date: If the email says 'start tomorrow', Foco sets the start date.
• Note: The full email (text, images, attachments) is attached to the task.

Example: Forwarding an email with the subject 'Urgent: Fix homepage bug for Client Z' creates a task titled 'Urgent: Fix homepage bug for Client Z' with the email attached. If the email says 'ASAP', Foco sets the priority to 'urgent'.

How to Organize Tasks After Consolidation (Exact Workflow)

1. Use Panorama Mode to Prioritize Across Projects

In Panorama mode, all tasks appear in one dashboard, each with its work’s color. Example: A freelancer with 3 clients sees:

• Client A (blue): 'Fix login bug' (GitHub, due today, urgent).
• Client B (green): 'Draft blog post' (Asana, due this week).
• Client C (red): 'Review contract' (email, due tomorrow).

Filter by due date (today, this week) or priority (urgent, important) to decide what to tackle first. Learn how to prioritize critical tasks across multiple jobs with the Critical Power List method.

2. Isolate a Project with Foco Mode

Click on a work to enter Foco mode. The dashboard shows only its tasks. Example: A developer working on 'Client X Development' sees only GitHub issues and Jira tickets for that client, with no distractions from other projects. Switch back to Panorama mode to see everything again.

3. Switch Views Based on Task Type

Use the View button to toggle between:

• List: Groups tasks by date (Today, This Week, Later, No Date). Example: A designer sees 'Today: 3 client reviews (Client A, Client B), 1 personal task'. Collapse the 'Done' section to hide completed tasks.
• Kanban: Custom columns (e.g., To Do, In Progress, Review, Done). Example: A developer drags a GitHub issue from 'In Progress' to 'Review' when ready for QA. On mobile, swipe between columns.
• Calendar: Weekly or monthly view (desktop) or daily (mobile). Tasks appear alongside Google Calendar or Outlook events. Example: A consultant sees '10:00-11:00: Client meeting (Google Calendar), 11:00-12:00: Draft proposal (Foco task)'. Learn how to time-block tasks from multiple clients without overlaps.

Why This Works for Multiple Jobs (vs. Alternatives)

Tools like Asana, Trello, or Notion are designed for single projects or teams, not for freelancers or small teams juggling multiple clients with different tools. Key differences:

• No seat minimums: Asana’s Starter plan costs 21.98 USD/month for 2 users (even if you work alone). Foco’s 4 EUR/month plan includes unlimited collaborators.
• Bidirectional sync: Asana’s GitHub/Jira integrations are one-way (view tasks in Asana, but can’t close them from Asana). Foco updates the original tool when you complete a task.
• Project isolation: Asana shows all tasks in one list, making it hard to focus on one client. Foco’s Foco mode filters tasks by project, and Panorama mode shows everything at once with colors for instant identification.
• Email capture: Asana has no native email capture. Foco extracts tasks from forwarded emails, attaching the full email as a note.
• No migration: Tools like ClickUp require you to move all tasks to their platform. Foco connects to your existing tools and brings tasks to you, without disrupting workflows.

Example: A freelance developer using GitHub for Client A, Jira for Client B, and Asana for Client C would need to check 3 apps constantly. With Foco, they see all tasks in one dashboard, mark a GitHub issue as done in Foco to close it in GitHub, and forward client emails to u-xxxx@in.heyfoco.com to create tasks automatically.

Common Mistakes to Avoid

• Not setting a destination work: If you leave it as 'Automatic' but don’t name your works clearly (e.g., 'Client X Development'), tasks may end up in the wrong place. Use fixed works for clients with one tool.
• Ignoring filters: Syncing all Jira issues (including internal ones) clutters your dashboard. Filter by project or label to reduce noise.
• Disabling 'Complete also in source': If you forget to enable this, you’ll need to manually close tasks in their original tool after completing them in Foco.
• Not using colors: Assign a unique color to each work (e.g., blue for Client A, green for Client B). Without colors, tasks blend together in Panorama mode.
• Forwarding emails without context: If an email subject is vague (e.g., 'Quick question'), the task title will be unclear. Edit the subject before forwarding or add a note in Foco.

How to Unify Tasks Without Losing Data (Practical Example)

A freelance designer works with 4 clients, each using a different tool:

• Client 1: GitHub for bug reports.
• Client 2: Jira for feature requests.
• Client 3: Asana for content tasks.
• Client 4: Email for urgent requests.

Before Foco, they spent 30 minutes daily switching between tools. After setup:

• GitHub: Connected to 'Client 1 Design' work (fixed destination). Tasks appear in Foco with the client’s color (purple).
• Jira: Connected to 'Client 2 Development' work (fixed). Filtered to sync only 'Design' project issues.
• Asana: Connected to 'Client 3 Content' work (fixed).
• Email: Forwarded to u-xxxx@in.heyfoco.com. Tasks appear in 'Client 4 Misc' work (automatic).

Now, they see all tasks in Panorama mode, filter by 'Today', and tackle them in order. When they mark a GitHub issue as done in Foco, it closes in GitHub automatically. Learn how to unify tasks from multiple apps without migrating data.

The goal isn’t to replace your tools, but to stop depending on them to remember what to do.

FAQ

Does Foco store my GitHub/Jira/Asana passwords?

No. Foco uses OAuth to connect to each tool, so you authorize access without sharing passwords. You can revoke access anytime from the tool’s settings.

What happens if I disconnect a tool from Foco?

Tasks already synced to Foco remain in your dashboard, but new tasks from that tool won’t appear. Disconnecting doesn’t delete tasks from the original tool.

Can I edit a task in Foco and sync changes back to the original tool?

No. Foco syncs task status (e.g., marking as done) but doesn’t push edits to the original tool. This prevents conflicts (e.g., if someone else edits the task in Jira).

How often does Foco sync tasks from connected tools?

Tasks sync within seconds of being assigned or updated in the original tool. There’s no manual refresh.

Can I use Foco’s email capture with Gmail or Outlook rules?

Yes. Set up a filter in Gmail or Outlook to forward emails matching certain criteria (e.g., from a client or with 'urgent' in the subject) to your u-xxxx@in.heyfoco.com address.