Creating and Managing Layers

Difficulty: Beginner to Intermediate

Overview

Creating and managing layers is fundamental to organizing complex taskboards in Waymaker. This comprehensive guide walks you through every aspect of layer management—from creating your first layer to building sophisticated hierarchical structures, configuring layer properties, reordering layers, and handling layer lifecycle operations like editing and deletion.

Whether you're setting up a simple two-layer structure for a small project or building a complex multi-level hierarchy for a large initiative, this article provides the step-by-step guidance you need.

What You'll Learn

• How to open the Layer Manager and navigate its interface
• Step-by-step instructions for creating root layers and sub-layers
• Complete guide to layer properties (name, description, dates, color, type)
• How to build nested layer hierarchies (parent-child relationships)
• Techniques for reordering layers with drag-and-drop
• How to edit layer properties after creation
• Safe layer deletion and task reassignment
• Best practices for layer organization and naming

Prerequisites

• A Waymaker account with access to taskboards
• An existing taskboard (or create one following Creating Your First Taskboard)
• Understanding of what layers are (see Introduction to Layers)
• Editor or Admin permissions on the taskboard

Accessing the Layer Manager

The Layer Manager is your central hub for all layer-related operations. It provides a visual, hierarchical view of all layers in your taskboard and controls for creating, editing, and organizing them.

Opening the Layer Manager

From the Sidebar (Recommended):

1. Open your taskboard
2. Look for the left sidebar (if collapsed, click the menu icon in the top-left)
3. Click the "Layers" section in the sidebar
4. The Layer Manager panel will expand, showing your layer hierarchy

Keyboard Shortcut (Future Feature):

• Press L to toggle the Layer Manager open/closed

Layer Manager Interface

The Layer Manager displays:

• Layer Hierarchy Tree: Visual representation of all layers with indentation showing parent-child relationships
• Layer Actions: Icons for editing, deleting, and reordering each layer
• Add Layer Button: Primary action to create new layers
• Layer Count: Total number of layers in the board
• Collapsed/Expanded States: Click arrows to expand or collapse nested layers

Visual Organization:

• Root layers appear at the left edge
• Child layers are indented beneath their parents
• Grandchild layers are indented further
• Each layer shows its name, type, and color indicator

Creating a Root Layer

Root layers are top-level organizational containers that don't have a parent layer. They're the foundation of your layer hierarchy.

Step-by-Step: Create Your First Root Layer

Step 1: Open the Layer Manager

• Navigate to your taskboard
• Open the left sidebar and locate the Layers section
• Click to expand the Layer Manager

Step 2: Click "Add Layer"

• Look for the "Add Layer" or "+" button at the top or bottom of the Layer Manager
• Click the button to open the layer creation modal

Step 3: Choose Layer Type

• The layer creation modal presents five type options:
  • Epic: For large features or initiatives (agile)
  • Sprint: For time-boxed iterations (agile)
  • Stage: For sequential phases (waterfall)
  • Milestone: For key deliverables or checkpoints
  • Custom: For flexible organizational needs
• Select the type that best fits your organizational need
• See Layer Types Explained for detailed guidance

Step 4: Enter Layer Name

• Type a clear, descriptive name for your layer
• Good Examples: "User Authentication Feature", "Sprint 10: Oct 1-14", "Discovery Phase", "Requirements Sign-off", "Q4 Initiatives"
• Avoid: Vague names like "Stuff", "Tasks", "Current"
• Layer names can be up to 100 characters but keep them concise

Step 5: Add Description (Optional)

• Enter a description explaining the layer's purpose, scope, or goals
• This appears when viewing layer details and helps team members understand the context
• Example: "This sprint focuses on completing the user authentication system, including login, password reset, and social auth integration."

Step 6: Set Date Range (Optional but Recommended)

• Start Date: When work in this layer begins
• End Date: When work in this layer should complete
• Dates are especially important for Sprint and Stage layer types
• Dates enable timeline visualizations (Gantt charts, Calendar view)
• Tip: Sprints typically have 1-4 week durations (most commonly 2 weeks)

Step 7: Choose a Color

• Select a color to visually distinguish this layer
• Colors appear in the layer dropdown, layer manager, and can be used in Kanban view
• Best Practice: Use consistent colors for layer types (e.g., all sprints blue, all epics purple)
• Accessibility: Choose colors with sufficient contrast

Step 8: Confirm Creation

• Review your layer details
• Click "Create Layer" or "Save"
• The new layer appears in your Layer Manager hierarchy
• You can now assign tasks to this layer

Example: Creating an Epic Layer

Let's create a layer for a "User Authentication" epic:

Layer Type: Epic
Name: User Authentication
Description: Complete user authentication system including login, password reset,
             OAuth providers (Google, GitHub), and two-factor authentication.
Start Date: October 1, 2025
End Date: November 30, 2025 (estimated)
Color: Purple (#8B5CF6)

After clicking "Create Layer", you'll see "User Authentication" appear as a root layer in your Layer Manager.

Creating Sub-layers (Nested Organization)

Sub-layers (also called child layers) are layers nested under a parent layer. This hierarchical structure lets you model complex organizational relationships.

When to Create Sub-layers

• Breaking Down Epics: Create Sprint sub-layers under Epic parent layers
• Dividing Phases: Create Stage sub-layers under Phase parent layers
• Organizing by Team: Create team sub-layers under department parent layers
• Time Breakdown: Create weekly or monthly sub-layers under quarterly parent layers

Step-by-Step: Creating a Sub-layer

Step 1: Identify the Parent Layer

• In the Layer Manager, find the layer that should be the parent
• Ensure this layer exists before creating children

Step 2: Open Sub-layer Creation

Option A: From the Layer Manager

• Hover over the parent layer
• Click the "Add Sub-layer" icon (often a "+" or nested icon)
• The creation modal opens with the parent pre-selected

Option B: From the Layer Creation Modal

• Click the main "Add Layer" button
• In the creation modal, find the "Parent Layer" dropdown
• Select the parent layer from the list
• This new layer will be created as a child of the selected parent

Step 3: Configure Sub-layer Properties

• Follow the same steps as creating a root layer:
  • Choose layer type
  • Enter name
  • Add description
  • Set date range
  • Choose color
• The only difference is that this layer will be nested under its parent

Step 4: Confirm Creation

• Click "Create Layer"
• The sub-layer appears indented beneath its parent in the Layer Manager
• You can now assign tasks to either the parent or child layer

Example: Creating Sprint Sub-layers Under an Epic

Building on our "User Authentication" epic, let's create Sprint sub-layers:

Sprint 1 Sub-layer:

Parent Layer: User Authentication (Epic)
Layer Type: Sprint
Name: Sprint 10: Oct 1-14
Description: Core authentication infrastructure—login UI, OAuth setup, basic tests
Start Date: October 1, 2025
End Date: October 14, 2025
Color: Blue (#3B82F6)

Sprint 2 Sub-layer:

Parent Layer: User Authentication (Epic)
Layer Type: Sprint
Name: Sprint 11: Oct 15-28
Description: Password reset flow, two-factor authentication, security hardening
Start Date: October 15, 2025
End Date: October 28, 2025
Color: Blue (#3B82F6)

Resulting Hierarchy:

User Authentication (Epic, Purple)
├── Sprint 10: Oct 1-14 (Sprint, Blue)
└── Sprint 11: Oct 15-28 (Sprint, Blue)

Creating Multiple Nested Levels

You can nest layers up to several levels deep, though we recommend 2-3 levels maximum for clarity.

Example: Three-Level Hierarchy

Product Launch (Root - Epic)
├── Authentication Feature (Child - Epic)
│   ├── Sprint 10: Oct 1-14 (Grandchild - Sprint)
│   └── Sprint 11: Oct 15-28 (Grandchild - Sprint)
└── Dashboard Feature (Child - Epic)
    ├── Sprint 11: Oct 15-28 (Grandchild - Sprint)
    └── Sprint 12: Oct 29-Nov 11 (Grandchild - Sprint)

To Create a Grandchild Layer:

1. Select the child layer as the parent (e.g., "Authentication Feature")
2. Create a new sub-layer under it (e.g., "Sprint 10")
3. The result is: Root → Child → Grandchild

Layer Properties: Complete Guide

Understanding each layer property helps you configure layers effectively for your workflow.

Name (Required)

Purpose: Primary identifier for the layer

Requirements:

• Must be unique within the board (no two layers with identical names)
• 1-100 characters
• Can include letters, numbers, spaces, and special characters

Best Practices:

• Be Specific: "Sprint 10: Oct 1-14" not "Current Sprint"
• Include Timeframes: "Q4 2025 Initiatives" not "Initiatives"
• Descriptive: "User Authentication Feature" not "Feature A"
• Consistent Format: If one sprint is "Sprint 10", make all sprints "Sprint XX"

Examples:

• ✅ "Mobile App Redesign Phase"
• ✅ "Sprint 15: Authentication & Security"
• ✅ "Q3 Marketing Campaign"
• ✅ "Requirements Sign-off Milestone"
• ❌ "Stuff" (too vague)
• ❌ "Current" (not specific)
• ❌ "Layer 1" (not descriptive)

Description (Optional)

Purpose: Detailed explanation of the layer's purpose, scope, and goals

Requirements:

• Optional but highly recommended
• Supports plain text or markdown formatting
• No character limit (but keep it concise)

Best Practices:

• Explain the Goal: What should be accomplished in this layer?
• Define Scope: What's included and excluded?
• List Success Criteria: How do you know when this layer is complete?
• Add Context: Why is this layer important?

Example Description for a Sprint:

Sprint 10 focuses on the core authentication infrastructure:

Goals:
- Complete login UI design and implementation
- Integrate OAuth providers (Google, GitHub)
- Write unit and integration tests for auth flows
- Begin password reset flow design

Success Criteria:
- Users can log in with email/password
- Users can log in with Google or GitHub
- All auth tests passing
- Password reset wireframes approved

Dependencies:
- Database schema must be finalized (Task #234)
- Design system components available

Start Date and End Date (Optional but Recommended)

Purpose: Define the timeframe for work in this layer

Requirements:

• Optional for all layer types except Sprint (where it's essential)
• Start date should be before or equal to end date
• Can be in the past, present, or future

Best Practices:

• Always Set for Sprints: Sprints are time-boxed by definition
• Set for Phases: Helps with project timeline visualization
• Optional for Epics: Epics span multiple sprints, dates are estimates
• Mandatory for Milestones: Milestone date is the deliverable deadline

Date Impact:

• Enables Gantt Chart view to show timeline
• Enables Calendar view to show layer timeframes
• Allows filtering by date range
• Helps calculate project duration
• Supports velocity and burndown calculations

Example Date Configurations:

Sprint (2 weeks):

• Start: October 1, 2025
• End: October 14, 2025

Phase (4 weeks):

• Start: October 1, 2025
• End: October 28, 2025

Epic (3 months estimate):

• Start: October 1, 2025
• End: December 31, 2025

Milestone (single day):

• Start: October 15, 2025
• End: October 15, 2025

Color (Optional)

Purpose: Visual distinction and quick identification

Requirements:

• Choose from predefined color palette or custom hex value
• Color appears in layer dropdowns, Layer Manager, and Kanban view

Best Practices:

• Consistent by Type: All sprints blue, all epics purple, all milestones gold
• Limit Palette: Use 4-6 colors maximum across all layers
• Sufficient Contrast: Ensure color is visible against backgrounds
• Meaningful Association: Blue for development, green for testing, gold for milestones

Common Color Schemes:

By Layer Type:

• Epic: Purple (#8B5CF6)
• Sprint: Blue (#3B82F6)
• Stage: Teal (#14B8A6)
• Milestone: Gold (#F59E0B)
• Custom: Gray (#6B7280)

By Priority:

• High Priority: Red (#EF4444)
• Medium Priority: Orange (#F97316)
• Low Priority: Green (#10B981)

By Team:

• Engineering: Blue (#3B82F6)
• Design: Pink (#EC4899)
• Marketing: Orange (#F97316)
• Operations: Green (#10B981)

Layer Type (Required)

Purpose: Categorizes the layer's organizational role

Options: Epic, Sprint, Stage, Milestone, Custom

Best Practices:

• Match Your Methodology: Use Sprint for agile, Stage for waterfall
• Consistent Usage: Don't mix types inconsistently (e.g., calling phases "Sprints")
• Type = Behavior: Some types have different behaviors (e.g., milestones are typically single-day)

See Layer Types Explained for detailed guidance on each type.

Parent Layer (Optional)

Purpose: Defines hierarchical relationships

Requirements:

• Optional—root layers have no parent
• Can only select existing layers as parents
• Cannot create circular relationships (a layer can't be its own ancestor)

Best Practices:

• Logical Hierarchy: Features under themes, sprints under epics
• Consistent Depth: Try to keep all branches at similar depth levels
• Limit Nesting: 2-3 levels maximum recommended

Reordering Layers with Drag-and-Drop

The Layer Manager supports drag-and-drop reordering so you can organize layers in the order that makes sense for your workflow.

How to Reorder Layers

Step 1: Open the Layer Manager

• Ensure the Layer Manager is visible in the left sidebar

Step 2: Locate the Layer to Move

• Find the layer you want to reorder in the hierarchy

Step 3: Drag the Layer

• Click and hold on the layer name or drag handle icon
• Drag the layer up or down to the desired position
• Visual indicators show where the layer will drop

Step 4: Drop into Position

• Release the mouse button to drop the layer
• The layer immediately reorders
• The new order saves automatically

Reordering Rules

Root Layer Reordering:

• Drag root layers up or down among other root layers
• Changes the display order in Layer Manager and layer dropdowns
• Does not affect child layers (they move with their parent)

Sub-layer Reordering:

• Drag sub-layers up or down among siblings (other children of the same parent)
• Can move a sub-layer from one parent to another (changes parent relationship)
• Cannot move a parent beneath its own child (circular reference prevention)

Visual Feedback:

• Drop Line: Horizontal line shows where layer will insert
• Indentation: Visual cues show whether dropping as sibling or child
• Not Allowed Cursor: Appears if drop location is invalid

Example: Reordering Sprints

Before:

User Authentication Epic
├── Sprint 11: Oct 15-28
├── Sprint 10: Oct 1-14
└── Sprint 12: Oct 29-Nov 11

After Reordering (chronological order):

User Authentication Epic
├── Sprint 10: Oct 1-14
├── Sprint 11: Oct 15-28
└── Sprint 12: Oct 29-Nov 11

How: Drag "Sprint 10" up and drop it above "Sprint 11".

Changing Parent Relationships

You can also use drag-and-drop to move a layer to a different parent or promote it to a root layer.

Make a Sub-layer into a Root Layer:

• Drag the sub-layer all the way to the left
• Drop it at the root level (un-indented)
• The layer is now a root layer with no parent

Move a Sub-layer to a Different Parent:

• Drag the sub-layer over the new desired parent
• Drop when the visual indicator shows it as a child of the new parent
• The layer moves to the new parent

Example:

Before:
Epic A
├── Sprint 1
Epic B
└── Sprint 2

Action: Drag "Sprint 1" to Epic B

After:
Epic A
Epic B
├── Sprint 2
└── Sprint 1

Editing Layer Properties

After creating a layer, you can edit any of its properties at any time (assuming you have appropriate permissions).

How to Edit a Layer

Step 1: Open the Layer Manager

• Navigate to your taskboard
• Open the Layer Manager in the left sidebar

Step 2: Locate the Layer

• Find the layer you want to edit in the hierarchy

Step 3: Open Edit Mode

Option A: Click the Edit Icon

• Hover over the layer in the Layer Manager
• Click the "Edit" icon (often a pencil or gear icon)
• The layer editing modal opens

Option B: Right-click Context Menu

• Right-click on the layer name
• Select "Edit Layer" from the context menu
• The editing modal opens

Step 4: Modify Properties

• The editing modal shows all current layer properties
• Modify any property: name, description, dates, color, type, or parent
• Note: Changing type may affect how the layer is used (e.g., Sprint → Stage)

Step 5: Save Changes

• Click "Save" or "Update Layer"
• Changes take effect immediately
• All tasks in the layer remain assigned (unless you change parent, which may prompt a warning)

What Can Be Edited

Always Editable:

• Layer name
• Layer description
• Start and end dates
• Layer color

Editable with Caution:

• Layer type: Changing type may affect methodology workflows (e.g., Sprint → Epic)
• Parent layer: Moving a layer to a new parent reorganizes hierarchy

Not Editable:

• Layer creation date
• Layer creator (owner)
• Layer ID (internal system identifier)

Editing Impact on Tasks

Name/Description/Color/Dates: No impact on tasks. They remain assigned to the layer with updated properties.

Parent Layer Change: If the layer has sub-layers, they move with it. Tasks in the layer remain assigned. May prompt confirmation if complex structure.

Type Change: No direct impact on tasks, but may change how the layer is interpreted in reports and visualizations.

Deleting Layers

Deleting a layer removes it from your taskboard permanently. Because tasks may be assigned to the layer, deletion requires careful handling.

Before You Delete

Ask Yourself:

1. Are there tasks in this layer? You'll need to reassign them.
2. Does this layer have sub-layers? You'll need to handle child layers.
3. Do I need this layer later? Consider archiving instead (future feature).
4. Is the layer referenced elsewhere? Some filters or reports may use it.

Alternatives to Deletion:

• Archive the Layer (future feature): Hide completed layers without deleting
• Rename the Layer: Repurpose it for future use
• Move Tasks First: Reassign all tasks, then delete the empty layer

How to Delete a Layer

Step 1: Open the Layer Manager

• Navigate to your taskboard
• Open the Layer Manager

Step 2: Locate the Layer

• Find the layer you want to delete

Step 3: Initiate Deletion

Option A: Delete Icon

• Hover over the layer
• Click the "Delete" icon (often a trash can)
• Confirmation dialog appears

Option B: Context Menu

• Right-click the layer
• Select "Delete Layer" from the menu
• Confirmation dialog appears

Step 4: Handle Tasks in the Layer

The system checks if any tasks are assigned to this layer:

If No Tasks:

• Simple confirmation: "Delete layer [name]?"
• Click "Delete" to confirm
• Layer is immediately removed

If Tasks Exist:

• Warning: "This layer contains X tasks. What should happen to them?"
• You have options:
  • Move tasks to another layer: Select a different layer from dropdown
  • Remove layer assignment: Tasks become "unassigned" (no layer)
  • Delete tasks: Permanently delete all tasks in the layer (⚠️ DANGEROUS)
  • Cancel: Don't delete the layer

Step 5: Handle Sub-layers

If the layer has child layers:

Option 1: Delete All

• Warning: "This layer has X sub-layers. Delete all?"
• If confirmed, all child layers and their tasks are handled per your selection
• Caution: This can affect many tasks if hierarchy is deep

Option 2: Promote Children

• Sub-layers become root layers (or move to parent's parent)
• Preserves sub-layer structure
• Tasks remain in their sub-layers

Option 3: Cancel

• Don't delete the parent layer
• Clean up structure manually first

Step 6: Confirm Deletion

• Review the impact summary
• Click "Delete Layer" to confirm
• The layer is removed immediately
• Warning: This action cannot be undone (currently)

Example: Deleting a Completed Sprint

Scenario: Sprint 10 is complete. All tasks are done. You want to delete the layer.

Step 1: Open Layer Manager, find "Sprint 10: Oct 1-14"

Step 2: Click Delete icon

Step 3: System says "This layer contains 12 tasks. What should happen to them?"

Step 4: You choose:

• Option A: "Move tasks to 'Archive' layer" (if you have an archive layer)
• Option B: "Remove layer assignment" (tasks exist but without layer)
• Option C: "Delete tasks" (if you're certain they're not needed)

Step 5: Confirm deletion

Result: Layer is deleted. Tasks are handled per your selection.

Task Reassignment Strategies

Strategy 1: Archive Layer

• Create a "Completed" or "Archive" custom layer
• Move all tasks from deleted layer to archive
• Keeps task history intact

Strategy 2: No Layer

• Remove layer assignment
• Tasks still exist in sections (Backlog, Done, etc.)
• Can be reassigned to new layers later

Strategy 3: Move to Active Layer

• If some tasks aren't truly complete, move to current sprint/phase
• Ensures work isn't lost

Strategy 4: Delete Tasks

• ⚠️ Use with extreme caution
• Only if tasks are truly obsolete
• Cannot be recovered

Deletion Best Practices

• Review First: Check all tasks in the layer before deleting
• Move Manually: For important layers, move tasks to new layers manually before deleting
• Archive Instead: If future reference needed, use archiving (when available)
• Delete Empty Layers: Safest to delete layers with zero tasks
• Communicate: If working with a team, notify before deleting shared layers
• Screenshot: Take a screenshot of the layer structure before major deletions

Building Complex Hierarchies: Complete Example

Let's walk through building a complete three-level layer hierarchy for a product development project.

Scenario: Product Launch Project

Goal: Build a product launch taskboard with themes, epics, and sprints.

Structure:

Product Launch (Root - Custom)
├── Authentication Feature (Child - Epic)
│   ├── Sprint 10: Oct 1-14 (Grandchild - Sprint)
│   ├── Sprint 11: Oct 15-28 (Grandchild - Sprint)
│   └── Sprint 12: Oct 29-Nov 11 (Grandchild - Sprint)
├── Dashboard Feature (Child - Epic)
│   ├── Sprint 11: Oct 15-28 (Grandchild - Sprint)
│   ├── Sprint 12: Oct 29-Nov 11 (Grandchild - Sprint)
│   └── Sprint 13: Nov 12-25 (Grandchild - Sprint)
└── Marketing Campaign (Child - Epic)
    ├── Pre-Launch Phase (Grandchild - Stage)
    ├── Launch Week (Grandchild - Stage)
    └── Post-Launch Follow-up (Grandchild - Stage)

Step-by-Step Construction

Step 1: Create Root Layer (Product Launch)

• Click "Add Layer"
• Type: Custom
• Name: "Product Launch"
• Description: "Q4 2025 product launch including authentication, dashboard, and marketing."
• Dates: Oct 1 - Dec 31, 2025
• Color: Navy (#001126)
• Parent: None (root layer)
• Click "Create Layer"

Step 2: Create First Epic (Authentication Feature)

• Click "Add Layer"
• Type: Epic
• Name: "Authentication Feature"
• Description: "Complete user authentication system with OAuth and 2FA"
• Dates: Oct 1 - Nov 11, 2025
• Color: Purple (#8B5CF6)
• Parent: Product Launch
• Click "Create Layer"

Step 3: Create Sprint Under Authentication Epic

• Click "Add Sub-layer" on Authentication Feature (or click "Add Layer" and select parent)
• Type: Sprint
• Name: "Sprint 10: Oct 1-14"
• Description: "Core auth infrastructure, login UI, OAuth setup"
• Dates: Oct 1-14, 2025
• Color: Blue (#3B82F6)
• Parent: Authentication Feature
• Click "Create Layer"

Step 4: Repeat for Additional Sprints

• Create "Sprint 11: Oct 15-28" under Authentication Feature
• Create "Sprint 12: Oct 29-Nov 11" under Authentication Feature

Step 5: Create Second Epic (Dashboard Feature)

• Click "Add Layer"
• Type: Epic
• Name: "Dashboard Feature"
• Parent: Product Launch
• Create sprints under it (Sprint 11, 12, 13)

Step 6: Create Third Epic (Marketing Campaign)

• Click "Add Layer"
• Type: Epic
• Name: "Marketing Campaign"
• Parent: Product Launch
• Create stages under it (Pre-Launch, Launch Week, Post-Launch)

Result: Complete three-level hierarchy ready for task assignment.

Tips & Best Practices

• Plan Before Building: Sketch your layer structure on paper before creating layers in the app
• Start Simple: Begin with 2-3 root layers. Add complexity as you understand your needs.
• Consistent Naming: Establish naming conventions early (e.g., "Sprint XX: MMM DD-DD")
• Use Colors Wisely: Stick to 4-6 colors maximum. Use them consistently by type or priority.
• Set Dates for Time-based Layers: Always include start/end dates for sprints, phases, and stages
• Descriptive Names: Layer names should be self-explanatory. "Sprint 10" is better than "Current Sprint"
• Limit Depth: Keep hierarchy to 2-3 levels. Deeper structures become confusing.
• Review Regularly: Clean up completed layers monthly. Archive or delete as appropriate.
• Document Your Structure: Add layer descriptions explaining purpose and scope
• Team Alignment: Ensure all team members understand the layer structure and conventions

Common Mistakes to Avoid

• Too Many Layers: Creating layers for every tiny grouping. Aim for 5-15 active layers, not 50+.
• Inconsistent Naming: "Sprint 10", "Sprint Eleven", "Current Sprint" all in the same board. Pick one format.
• No Dates: Forgetting to set dates on sprints and phases. This breaks timeline views.
• Circular Parents: Trying to make a layer its own ancestor. The system prevents this, but don't try.
• Deleting Without Checking: Deleting layers without reviewing task impact. Always check first.
• Wrong Type: Using "Sprint" for waterfall phases or "Stage" for agile iterations. Match type to methodology.
• Over-nesting: Creating 5+ levels of hierarchy. This makes navigation painful.
• Vague Names: "Layer 1", "Group A", "Current". Be specific and descriptive.
• Ignoring Hierarchy: Creating flat structure when hierarchy would add clarity, or vice versa
• No Team Input: Building layer structure without consulting team members who'll use it

Related Articles

• Introduction to Layers - Understand what layers are and when to use them
• Layer Types Explained - Deep dive into Epic, Sprint, Stage, Milestone, and Custom types
• Using Layers for Agile Projects - Complete agile workflow with epics and sprints
• Using Layers for Waterfall Projects - Waterfall project setup with phases and stages
• Filtering and Viewing by Layer - Focus on specific layers
• Layer Progress Tracking - Monitor layer completion
• Layer Best Practices - Advanced organization strategies

Need More Help?

If you have questions about creating or managing layers, or need assistance building your layer structure, please contact support or visit our community forums. Our team can help you design the perfect organizational structure for your projects.