Skip to content

Working with Projects

DubPlanner works with your existing Linear projects to provide weekly sprint planning capabilities. Projects are created and managed in Linear, and DubPlanner provides a visual planning interface on top of them.

Projects in DubPlanner are Linear projects that you’ve already created in your Linear workspace. DubPlanner doesn’t create new projects—instead, it connects to your existing Linear projects and provides a drag-and-drop planning interface for organizing work across weeks.

When you open DubPlanner:

  1. Login with Linear: Authenticate using your Linear account
  2. View Available Projects: The sidebar lists your teams; expand one to see its projects
  3. Select a Project: Click on a project to open it in the planning view
  4. Start Planning: The weekly planning grid loads with all issues from that project

Once you have more than a handful of projects, use the search box at the top of the sidebar — it finds projects across every team by project or team name — and star the ones you return to so they sit in Favourites. DubPlanner also reopens the last project you were in. See Search & navigation.

For a project to work well with DubPlanner, it should have:

  • Set in Linear project settings
  • Determines the first week of your planning grid
  • If not set, defaults to 19 weeks from the current date
  • Set in Linear project settings
  • Determines how many weeks to initially display
  • Can be adjusted if you need more weeks for planning
  • Automatically pulled from Linear project membership
  • Shows as rows in the planning grid
  • Members can be assigned issues by dragging and dropping
  • All Linear issues in the project appear in DubPlanner
  • Issues start in the Backlog (unscheduled area)
  • Drag issues onto the grid to assign them to team members and weeks

Once you’ve selected a project, you’ll see:

  • Columns: Weeks (starting from the project start date)
  • Rows: Team members + “Unassigned” row
  • Cells: Issues assigned to specific team members for specific weeks
  • Current Week: Highlighted to show where you are in the timeline
  • Located below the planning grid
  • Shows all unscheduled issues from the project
  • Switch between card view and table view
  • Use the search bar to find specific issues
  • Appears above the planning grid
  • Shows when each milestone is scheduled to complete
  • Calculated based on the latest issue assigned to that milestone
  • Color-coded for easy identification

DubPlanner maintains a two-way sync with Linear:

  • New Issues: Automatically appear in the Backlog
  • Issue Updates: Title, description, status changes sync immediately
  • Assignments: Team member assignments reflect Linear state
  • Deletions: Removed issues disappear from DubPlanner
  • Week Assignments: Creates “Week[N]” labels in Linear
  • Status Changes: Updates issue state in Linear
  • Assignments: Updates assignee in Linear
  • Deletions: Permanently removes issues from Linear (with confirmation)

Project settings are managed in Linear:

  1. Open the project in Linear
  2. Go to Project Settings
  3. Update the Start Date
  4. Refresh DubPlanner to see the updated timeline
  1. Open the project in Linear
  2. Go to Project Settings
  3. Update the Target Date
  4. Refresh DubPlanner to extend the visible weeks

Milestones are created and managed in Linear:

  1. Open the project in Linear
  2. Go to Milestones
  3. Create a new milestone
  4. Assign issues to the milestone in Linear
  • Milestones appear in a row above the planning grid
  • Only shows if the milestone has at least one issue with a week assignment
  • The milestone is displayed in the week of its latest assigned issue
  • Color-coded circles help visually distinguish milestones

To change when a milestone will be completed:

  1. Drag the issues assigned to that milestone to different weeks
  2. The milestone marker automatically moves to the latest week
  3. This helps you visualize whether you’re on track

To work on a different project:

  1. Click the project selector in the header
  2. Choose a different project from the list
  3. The planning grid updates to show the new project
  4. Your last viewed project is remembered for next time

If you work on multiple projects:

  • Each project has its own independent planning grid
  • Team availability can be marked project-specific
  • Switch between projects using the project selector
  • Recent projects are shown for quick access

DubPlanner respects Linear’s permission model:

  • View: If you can view a project in Linear, you can view it in DubPlanner
  • Edit: If you can edit issues in Linear, you can move them in DubPlanner
  • Delete: If you can delete issues in Linear, you can delete them in DubPlanner
  • Admin: Project settings are managed in Linear
  • Set accurate dates: Start and target dates help with realistic planning
  • Create milestones early: Define your major deliverables upfront
  • Import all issues: Make sure all work is tracked in Linear
  • Start with milestones: Plan milestone completion dates first
  • Assign critical issues: Prioritize important work first
  • Check availability: Review team availability before assigning work
  • Balance workload: Distribute work evenly across team members
  • Leave buffer: Don’t pack weeks too tightly—leave room for unexpected work
  • Regular updates: Keep issue status current in either Linear or DubPlanner
  • Communicate changes: Let team know when you move work around
  • Review weekly: Check the plan at the start of each week
  • Adjust as needed: Don’t be afraid to re-plan when priorities change
  • Check Linear access: Ensure you’re a member of the project in Linear
  • Refresh the page: Sometimes a refresh is needed to see new projects
  • Re-authenticate: Try logging out and back in
  • Update the project start date in Linear
  • Refresh DubPlanner to reload the project
  • Check if issues are archived in Linear
  • Verify issue is assigned to the correct project
  • Try refreshing the page
  • Verify you have edit permissions in Linear
  • Some issue states may be read-only depending on your workflow