Column Settings

Each column on your Kanban board represents a workflow stage. The column settings let you customize how each stage appears and behaves, including its name, color, and status type classification.

The Problem This Solves

A generic "To Do" and "Done" workflow does not match how your team actually works. Different teams have different processes: some need review stages, others need testing columns, and many have multiple in-progress states for different work types.

Column settings let you build a workflow that reflects your actual process. When the board matches how work flows through your team, updates happen naturally and the board stays accurate.

What You Are Looking At

The Column Settings modal appears when you select "Column Settings" from a column's dropdown menu. The modal shows the current column name at the top for reference, followed by form fields for customizing the column properties.

Opening Column Settings

To access column settings:

1. Locate the column you want to configure on your Kanban board
2. Click the three-dot menu icon in the column header
3. Select "Column Settings" from the dropdown menu

You need board management permissions to access this option. If you do not see the menu, contact your workspace administrator.

Column Title

The title field displays at the top of the column and helps team members understand what stage work has reached. Choose clear, action-oriented names that describe the state of work in that column.

Effective column names:

• Backlog (work not yet started)
• In Progress (actively being worked)
• Code Review (waiting for peer review)
• QA Testing (verification in progress)
• Done (completed and verified)

Less effective names:

• Column 1 (meaningless)
• Tasks (too generic)
• Bob's stuff (person-specific, not state-specific)

The title supports up to 25 characters. Keep names short enough to display cleanly in the column header across different screen sizes.

Column Color

The color picker lets you assign a distinctive color to each column. This color appears as a top border on the column and helps with visual scanning across the board.

Color strategies:

• Use consistent colors for similar status types (all "in progress" columns in blue)
• Use red sparingly for blocked or critical states
• Use green for completion columns
• Maintain enough contrast between adjacent columns

Click the color input to open your browser's native color picker. Select any color from the palette or enter a specific hex code for brand-consistent colors.

Status Type Classification

The status type dropdown classifies how this column fits into your overall workflow. This classification affects metrics, reports, and certain automation behaviors.

To Do (State 0) Columns classified as "To Do" represent work that has not started. Tasks in these columns:

• Count toward backlog metrics
• Do not count toward work-in-progress limits in some calculations
• Represent future work when forecasting

In Progress (State 2) Columns classified as "In Progress" represent active work. Tasks in these columns:

• Count toward work-in-progress metrics
• Contribute to cycle time when they enter and exit
• Represent current team capacity usage

Done (State 1) Columns classified as "Done" represent completed work. Tasks in these columns:

• Count toward throughput metrics
• Stop accumulating cycle time
• May trigger completion notifications or automations

Choosing the correct status type ensures your analytics accurately reflect team performance and workflow efficiency.

Saving Changes

After adjusting settings, click the confirm button to save your changes. The column updates immediately on the board for all team members. You can also click cancel or press Escape to discard changes and close the modal without saving.

A loading indicator appears while the save operation processes. Wait for confirmation before navigating away.

Impact on Existing Tasks

Changing column settings affects only the column properties, not the tasks within it. Tasks remain in the column with their existing assignments, dates, and other properties. The column simply displays with the new name and color.

If you need to reorganize which tasks belong in which column, drag tasks between columns after updating the settings.

Column Reordering

Column settings control individual column properties. To change the order of columns on your board, drag the column header itself to reposition it. Columns can be reordered independently from their status type classification.

Pro Tips

• Workflow visualization: Use color gradients from left to right (cool colors for backlog, warm colors for active, green for done) to create visual flow
• Status accuracy: Review your status type classifications if metrics seem wrong. A "QA Queue" column should usually be "To Do" not "In Progress" since work is waiting, not active
• Team consensus: Discuss column names with your team. Everyone should agree on what it means for a task to be in each column

Permissions

Column settings require board management permissions. Agency Owners and Managers typically have this permission by default. Developers may have it depending on workspace configuration.

How to Report a Problem or Request a Feature

Your feedback matters. Here is how to share it:

If you encounter issues with column settings or want to suggest additional configuration options, we want to know.

In the Sidebar, click on Support Tickets and open a ticket for the problem. Everything is interactive and fast through the GitScrum Studio platform.

Create Column Modal

The Create Column modal lets you add new workflow stages to your Kanban board. Columns represent the stages tasks move through from start to completion.

What You Are Looking At

When you click the "Column" button in the Kanban board header, a modal appears with fields for configuring the new column. The modal is compact and focused on the essential settings needed to create a functional workflow column.

Column Title and Color

Title

Enter a descriptive name for your column. Common column titles include:

• Backlog - Tasks waiting to be started
• To Do - Tasks ready for the current iteration
• In Progress - Tasks currently being worked on
• In Review - Tasks awaiting review or approval
• Testing - Tasks being validated
• Done - Completed tasks

Choose names that match your team's terminology and workflow. Consistency helps team members understand where tasks belong without additional explanation.

Color

Click the color picker to select a column accent color. This color appears as a top border on the column and helps visually distinguish workflow stages.

Consider using a color progression:

• Cool colors (blue, gray) for early stages
• Warm colors (yellow, orange) for active work
• Green for completion
• Red for blocked or attention-needed stages

Column Status

The status dropdown determines how the column affects task state calculations:

Open

Tasks in Open columns are considered not yet started. This is typically used for backlog columns where tasks wait to be picked up.

Open columns:

• Tasks count toward "total" but not "in progress" or "completed"
• Contribute to backlog metrics
• Typically appear on the left side of the board

In Progress

Tasks in In Progress columns are actively being worked on. This status affects capacity calculations and work-in-progress metrics.

In Progress columns:

• Tasks count toward "in progress" metrics
• Affect team utilization calculations
• Can have WIP limits applied
• Typically appear in the middle of the board

Closed

Tasks in Closed columns are considered complete. Moving a task to a Closed column marks it as done for metrics and reporting.

Closed columns:

• Tasks count toward "completed" metrics
• Contribute to velocity calculations
• Drive progress percentage on project cards
• Typically appear on the right side of the board

Creating the Column

After filling in the title, selecting a color, and choosing a status, click "Create" to add the column to your board. The column appears at the right side of the board and can be repositioned by dragging.

New columns start empty. Move existing tasks into the column or create new tasks directly in it.

Pro Tips (Once You Are Comfortable)

• Time-saver: Create all your columns before adding tasks. This prevents having to reorganize work later.

• Did you know? Columns can be reordered by dragging them. Hold the column header and drag left or right to change position.

• Common mistake: Creating too many columns. Start minimal (3-4 columns) and add more only when your workflow genuinely needs them. Too many columns create confusion and slow down work.

• Power move: Use column colors strategically. A visual pattern (left to right, cool to warm) helps new team members understand workflow direction instantly.

Permissions

Only Agency Owners and Managers with the "manage_boards" permission can create columns. If you do not see the Column button, your role may not have this permission.

How to Report a Problem or Request a Feature

If you encounter issues creating columns or have suggestions, submit feedback through GitScrum Studio. In the Sidebar, click on Support Tickets and open a ticket describing your request.

Create Task

The task creation modal provides a streamlined interface for adding new work items to your projects. Whether you are capturing a quick bug report, documenting a feature request, or creating a detailed technical task, this modal gives you the flexibility to include exactly the information you need without forcing unnecessary fields.

The Problem This Solves

Creating tasks should take seconds, not minutes. Traditional project management tools force you through multi-page wizards or require filling out dozens of fields before you can save anything. This kills momentum and discourages team members from capturing work items as they think of them.

The Create Task modal eliminates this friction by requiring only the essentials: a project and a title. Everything else is optional and available when you need it, hidden when you do not.

What You Are Looking At

The Create Task modal appears as a centered dialog with a clean, focused interface. At the top you will find workspace and project selectors, followed by the task title field. Below that, a row of compact dropdown buttons provides quick access to additional options like workflow status, priority, assignee, labels, and time estimates.

The modal uses the same visual language as your IDE: monospace fonts for metadata, high contrast text, and keyboard-friendly navigation throughout.

Opening the Create Task Modal

You can open the Create Task modal from multiple locations throughout GitScrum Studio:

From the Kanban Board:

• Click the "New Task" button in the board header
• Use the keyboard shortcut displayed in the button tooltip
• Click the "+" icon that appears when hovering over any column header

From anywhere in the application:

• Use the global quick create shortcut
• Click the "+" button in the main navigation sidebar
• Right-click context menus in task lists

Context-aware creation: When you open the modal from within a specific project, the workspace and project fields automatically populate with the current context. This saves time and reduces errors when creating multiple tasks.

Required Fields

The modal enforces minimal requirements to get a task created quickly:

Project Selection Before you can create a task, you must select which project it belongs to. If you are already viewing a project, this selection happens automatically. Otherwise, first select a workspace, then choose a project from that workspace.

The workspace dropdown shows all workspaces you have access to, sorted by most recently used. After selecting a workspace, the project dropdown populates with available projects in that workspace.

Task Title The title field accepts up to 255 characters. Write something descriptive enough that team members understand what the task involves without needing to open it. Good titles follow a consistent format across your team, such as starting with a component name or using a verb-noun pattern.

The title field auto-focuses when the modal opens, so you can immediately start typing.

Optional Fields

All remaining fields enhance your task with additional context but none are required for creation:

Workflow Status

The workflow dropdown shows all available statuses from your project's configured workflow. Each status displays with its assigned color for quick visual identification. Select the starting column where this task should appear on your Kanban board.

If you do not select a workflow status, the task defaults to the first column in your project's workflow, typically a "Backlog" or "To Do" column.

Priority Level

Priority indicates the relative importance and urgency of a task. Your project administrator configures the available priority levels, which might include options like Critical, High, Medium, and Low.

Selecting a priority helps team members understand which tasks need attention first during sprint planning or daily work. Tasks with higher priorities typically appear with visual indicators on the board.

Task Type

Task types categorize work into logical groups such as Bug, Feature, Improvement, Documentation, or Technical Debt. Each type displays with a color indicator matching your project configuration.

Using consistent task types enables filtering and reporting by category. Your team can analyze how much time goes toward bug fixes versus new features, or track documentation tasks separately from development work.

Assignee

The assignee dropdown shows all members with access to the selected project. A search field at the top lets you filter the list by typing part of a member's name.

You can leave the assignee blank for tasks that need triage or selection during team meetings. Alternatively, assign yourself to claim ownership immediately, or assign a specific team member who should handle the work.

Selecting "No assignee" explicitly clears any previous assignment selection.

Labels

Labels provide flexible categorization beyond the structured task type system. You can attach multiple labels to a single task, enabling cross-cutting concerns like "needs-review", "blocked", "customer-reported", or technical domain tags.

The labels dropdown shows all labels configured for the project. Click a label to toggle its selection. A checkmark appears next to selected labels. The button displays a count when you have selected one or more labels.

Time Estimate

Time estimation lets you predict how long a task will take to complete. This feature appears with a "Pro" badge indicating it requires a paid subscription.

The estimate interface provides separate hour and minute selectors. Choose values that represent your best guess at the total effort required. You can clear the estimate using the "Clear" button if you need to remove a previously set value.

Time estimates enable velocity tracking, sprint capacity planning, and burndown chart accuracy. They work best when your team commits to honest estimates and updates them as understanding improves.

Board Selection

If your project uses multiple boards, this dropdown lets you specify which board should display the task. Some teams use separate boards for different aspects of work, such as a main development board and a dedicated bug triage board.

When only one board exists, this field may be hidden or disabled as there is only one valid option.

The Description Field

Below the quick option buttons, an expandable description area accepts longer text explaining the task in detail. Click to expand the text area and write acceptance criteria, reproduction steps, technical notes, or any context that helps others understand the work.

The description supports markdown formatting, letting you include code blocks, lists, links, and other structured content. Preview your formatting by saving the task and viewing it in the task detail panel.

Creating Multiple Tasks

The "Create more" toggle at the bottom left of the modal enables rapid task entry mode. When enabled, successfully creating a task clears the form and keeps the modal open so you can immediately create another task.

This proves useful during brainstorming sessions, sprint planning, or when breaking down a large feature into multiple work items. The workspace and project selections persist between creations, so you only need to enter the changing information.

Keyboard Navigation

The Create Task modal supports full keyboard navigation:

• Tab: Move between fields in order
• Shift+Tab: Move to the previous field
• Enter: Submit the form when the create button is focused
• Escape: Close the modal without creating
• Arrow keys: Navigate dropdown options when a dropdown is open
• Enter: Select the highlighted dropdown option

When a dropdown is open, you can type to filter options in some fields like the assignee selector.

Validation and Errors

The modal prevents submission until you meet the minimum requirements: a selected project and a non-empty title. The create button remains disabled and visually muted until these conditions are satisfied.

If a creation attempt fails due to network issues or server-side validation, an error message appears explaining what went wrong. Your entered data remains in the form so you can fix the issue and try again without retyping everything.

After Creating a Task

Upon successful creation, the modal behavior depends on your "Create more" setting:

Create more disabled: The modal closes and the new task appears on your Kanban board in the appropriate column. The board may scroll to ensure the new task is visible.

Create more enabled: The modal remains open with cleared fields. A brief success indicator shows the task was created, often with a link to view the created task directly.

In both cases, the Kanban board updates in real-time to display the new task. Other team members viewing the same board see the task appear automatically without refreshing.

Pro Tips

• Capture first, organize later: Create tasks with just a title to capture ideas quickly. Return later to add details, estimates, and assignments during refinement.

• Use templates: If your team has standard formats for certain task types, keep a text file with templates you can paste into descriptions.

• Keyboard shortcuts: Learn the global shortcut for opening the create modal. Experienced users can create a task in under 5 seconds without touching the mouse.

• Context matters: Opening the modal from a specific column on the board can automatically set the workflow status, reducing required clicks.

How to Report a Problem or Request a Feature

Your feedback matters. Here is how to share it:

If you encounter issues with the task creation modal or have ideas for improving the workflow, we want to hear from you. Clear descriptions of what you expected versus what happened help us investigate and fix issues faster.

In the Sidebar, click on Support Tickets and open a ticket for the problem. Everything is interactive and fast through the GitScrum Studio platform.

Advanced Search and Filters

The Advanced Search modal provides powerful filtering capabilities to find specific tasks across your project. Whether you need to locate a task by number, find all blocked items, or filter by date ranges, this tool handles complex queries that simple text search cannot.

The Problem This Solves

As projects grow, finding specific tasks becomes increasingly difficult. Scrolling through columns or remembering task codes wastes time. You need to answer questions like "What tasks did the team complete last week?" or "Which bugs are currently unassigned?" without manually checking each item.

Advanced Search lets you build precise queries combining multiple criteria. Find exactly what you need in seconds, regardless of project size.

What You Are Looking At

The Advanced Search modal appears as a centered form with multiple filter fields organized in a grid. At the top, you see task number and title fields. Below that, dropdowns and date pickers let you narrow results by workflow status, team members, dates, labels, types, efforts, sprints, and user stories.

Opening Advanced Search

To access Advanced Search:

1. Navigate to your project's Kanban board
2. Click the menu button in the toolbar (three-dot icon or hamburger menu)
3. Select "Advanced Search" from the dropdown menu

The modal opens with all filters cleared, ready for you to specify your search criteria.

Search by Task Identifier

Task Number

Every task has a unique code combining the project prefix and a sequential number. Enter just the numeric portion in the task number field. The project prefix displays automatically to the left of the input.

If you know the exact task code (like #PROJ-123), enter "123" in this field. The search returns that specific task immediately.

Task Title

Search for words or phrases appearing in task titles. This performs a partial match, so searching for "login" finds "Fix login button", "Login page redesign", and "User login flow".

Combine title search with other filters to narrow results. For example, search for "API" in titles while filtering to a specific assignee.

Filter by Workflow Status

The workflow dropdown shows all status columns configured for your project. Select a workflow status to see only tasks currently in that column.

This filter works across all boards if you have multiple boards in the project. To see only tasks from a specific board, first select that board in the main toolbar before opening Advanced Search.

Search in Description

The description field searches within task description content, not just titles. This helps find tasks where the key information lives in the detailed description rather than the brief title.

Description search is particularly useful for finding tasks that reference specific technical details, error messages, or requirements text.

Filter by Team Members

The team members selector shows all project members. Select one or more members to filter tasks where they are assigned.

Selection options:

All Members: When checked, the search includes tasks assigned to any team member. This excludes unassigned tasks.

All Tasks: When checked, the search includes both assigned and unassigned tasks, essentially removing the assignee filter.

Specific members: Multi-select individual members to see only tasks assigned to those people. Hold Ctrl/Cmd while clicking to select multiple members.

This filter helps answer questions like "What is Sarah working on?" or "Show me tasks assigned to the frontend team."

Date Range Filters

Multiple date range filters let you find tasks based on their timeline:

Start Date Range

Filter tasks by their scheduled start date. Specify a "from" date, a "to" date, or both to define a range.

Use this to find work scheduled to begin during a specific period, useful for sprint planning or resource forecasting.

End Date Range

Filter tasks by their due date or scheduled end date. Like start date, specify one or both bounds.

Use this to find upcoming deadlines or tasks that were due during a past period.

Created At Range

Filter by when tasks were created in the system. This helps with questions like "What new tasks appeared this week?" or "Show me tasks created in Q3."

Closed At Range

Filter by when tasks were marked complete. Perfect for retrospectives and reports covering specific time periods. Find all tasks your team finished last month without manually tallying.

Clearing Dates

Each date field has a clear button (red X) that appears when a value is set. Click to remove that specific date constraint while keeping other filters active.

Filter by Labels

The labels selector shows all labels configured for your project. Select one or more labels to filter tasks tagged with those labels.

Labels provide cross-cutting categorization. Use this filter to find all "customer-reported" tasks or everything tagged "needs-documentation."

Filter by Task Type

The types dropdown shows your project's configured task types (Bug, Feature, Improvement, etc.). Select a type to see only matching tasks.

Combine type filtering with other criteria. For example, show all bugs created this week, or all features assigned to a specific developer.

Filter by Effort Level

The effort dropdown shows configured effort or priority levels. Select one to filter tasks by their assigned effort.

Use this to find high-priority items needing attention or to see the distribution of effort levels across your backlog.

Filter by Sprint

The sprints dropdown shows all sprints in your project. Select a sprint to see tasks assigned to that iteration.

This helps review sprint scope without navigating to the sprint detail page. Combine with other filters to answer questions like "What bugs are in Sprint 12?"

Filter by User Story

The user stories dropdown shows all user stories in your project. Select a user story to see tasks linked to that feature or epic.

Use this to review progress on a specific feature or ensure all related tasks are properly tracked.

Task Status Filter

Filter tasks by their overall status:

• All: Include tasks in any state
• Active: Show only non-archived, non-draft tasks
• Archived: Show only archived tasks
• Draft: Show only draft tasks

This helps you find archived items you need to restore or review draft tasks awaiting refinement.

Task Flags

Checkbox flags filter by special task states:

Is Blocker: When checked, show only tasks marked as blocked. These tasks cannot proceed due to external dependencies.

Is Bug: When checked, show only tasks classified as bugs. This typically matches the Bug task type but may include additional bug-related flags.

Unassigned: When checked, show only tasks without any assignees. Use this during sprint planning to find work needing assignment.

Multiple flags can be combined. Check both "Is Blocker" and "Unassigned" to find blocked tasks that nobody is currently addressing.

Executing the Search

Click the "Search" button to apply your filters and execute the query. Results update on the board view, showing only tasks matching all specified criteria.

The search remains active until you clear it. You can tell a search is active by visual indicators in the toolbar.

Clearing the Search

To remove all filters and return to viewing all tasks:

1. Open Advanced Search again
2. Click "Cancel" to close without searching
3. Or manually clear each field and search again

Some interfaces provide a "Clear filters" button in the toolbar for quick reset.

Search Tips

Start broad, then narrow: Begin with one or two filters. If results are too many, add more criteria. If results are empty, remove some filters.

Combine strategically: Powerful queries combine filters that intersect meaningfully. "Bugs + Last Week + High Priority" quickly shows urgent issues.

Date ranges for reports: Use created/closed date ranges to generate time-bounded reports without exporting data.

Save common searches: Note down filter combinations you use frequently. Some teams document these in their project wiki for easy reference.

Pro Tips

• Task number shortcut: If you know the exact task code, the task number search is fastest
• Description search depth: Description search examines the full text, finding deeply buried references
• Multiple assignees: Filter by multiple team members to see a sub-team's complete workload
• Sprint comparison: Run the same search against different sprints to compare velocity or patterns

How to Report a Problem or Request a Feature

Your feedback matters. Here is how to share it:

If search results seem incorrect, filters do not work as expected, or you want additional search capabilities, we want to know.

In the Sidebar, click on Support Tickets and open a ticket for the problem. Everything is interactive and fast through the GitScrum Studio platform.

Task Detail Panel

When you click any task on your Kanban board, a detailed panel slides in from the right side of your screen. This panel provides comprehensive access to all task information, editing capabilities, and related actions without leaving the board context.

The Problem This Solves

Jumping between a task list and individual task pages creates friction and loses context. You want to quickly check task details, update status, or add comments while keeping the board visible in your peripheral vision. The task detail panel solves this by overlaying task information without navigating away.

This approach follows the same pattern you find in modern email clients and IDEs: select an item from a list, see its details in a panel, make edits inline, then move to the next item.

What You Are Looking At

The task detail panel consists of two main areas: a content column on the left and a metadata sidebar on the right. The panel appears as a drawer from the right side of your screen, with a semi-transparent overlay dimming the board behind it.

The header shows breadcrumb navigation (workspace / project / task code), time tracking controls, and utility buttons for favorites, calendar, and closing. Below that, the content area displays the task title, description, checklists, related items, and comments. The right sidebar presents all metadata fields in a scannable format.

Panel Header Components

Breadcrumb Navigation

At the top left, you see the full context path: workspace name, project name, and task code. Each segment helps you confirm you are viewing the correct task, especially when working across multiple projects.

Time Estimate Progress

A visual indicator shows estimated versus tracked time. Click this element to open the time estimate modal where you can adjust the estimate. When tracked time exceeds estimates, the indicator shifts color to signal the overrun.

Time Tracking Controls

The time tracking button lets you start, pause, or stop a timer for this task. Active timers continue running even if you close the panel, making it easy to track work across your session.

Modal Toggle

Switch between drawer mode and modal mode. Drawer mode keeps the panel attached to the right edge with the board partially visible behind. Modal mode centers the task panel and expands it for focused editing.

Favorite Toggle

Mark tasks as favorites for quick access. Favorited tasks appear in your personal favorites list, separate from project organization.

Calendar Integration

Add this task to your calendar application. The integration creates calendar events with task details, helping you block time for specific work items.

Main Content Area

The left column provides the primary working area for task content.

Task Title

The title appears prominently and supports inline editing. Click the title text to enter edit mode, make your changes, then click outside or press Enter to save. The title editor validates length and required characters automatically.

Below the title, metadata shows when the task was created and by whom, providing historical context.

Cover Image

If the task has an attached cover image, it displays prominently below the title. Tasks can have image attachments that serve as visual references or mockups. The image carousel supports multiple images when available.

Description

The description section supports rich text editing with markdown formatting. Click the edit button to activate the editor, then write or modify the description. The editor supports:

• Headers and text formatting
• Bullet and numbered lists
• Code blocks with syntax highlighting
• Links and images
• Task mentions using @ notation

Save your changes by clicking outside the editor or using keyboard shortcuts.

Checklists

Create checklist items to break tasks into smaller, trackable steps. Check items off as you complete them. The checklist shows overall progress and supports reordering items via drag and drop.

Add new checklist items using the input field at the bottom of any checklist. Create multiple checklists to organize different aspects of a task, such as "Development Steps" and "QA Verification".

Tabs Section

Below the core content, tabs provide access to related information:

• Subtasks: Child tasks linked to this parent task
• Attachments: Files uploaded to this task
• Links: External references and related URLs
• Activity: Chronological log of all changes

Each tab loads content on demand, keeping the initial panel load fast.

Comments

The comments section sits at the bottom of the content area. View existing comments with author, timestamp, and content. Add new comments using the input field. Comments support markdown formatting and @mentions to notify team members.

Metadata Sidebar

The right column organizes all task metadata in scannable sections.

Board Selection

If your project uses multiple boards, select which board displays this task. This affects where the task appears without changing other properties.

Workflow Status

The workflow dropdown shows all available statuses from your project's workflow configuration. Each status displays with its assigned color. Changing the workflow status here instantly moves the task to the corresponding column on the Kanban board.

Flags Section

Toggle important task states:

Draft: Mark tasks as drafts when they need refinement before work begins. Draft tasks may be excluded from certain reports and views.

Archived: Archive completed or abandoned tasks to remove them from active views without deleting. Archived tasks remain searchable and recoverable.

Blocked: Flag tasks that cannot proceed due to external dependencies. When you mark a task as blocked, you can record who blocked it and why, making blockers visible to the team.

Assignees

View current assignees with their avatars and names. Click to open the member selector and add or remove assignees. Each assignee shows as a linked card you can click to view their profile.

Tasks without assignees display an empty state prompting assignment. Multiple assignees work well for pair programming or tasks requiring coordination.

Labels

View and edit attached labels. Labels display as colored badges with their names. Click to open the label selector where you can toggle labels on and off.

Task Type

Set the task type (Bug, Feature, Improvement, etc.) using the dropdown. Each type displays with its configured color, matching how tasks appear on the board.

Effort Level

Select the effort or priority level for this task. Effort levels help with prioritization and workload balancing.

Dates

Configure task dates including:

• Start Date: When work should begin
• Due Date: When the task should be complete
• Custom Date Fields: Any additional date fields your project has configured

Click date fields to open a date picker with calendar navigation.

Git Branches

View linked Git branches associated with this task. When you create branches following naming conventions that include the task code, they automatically link here. This provides traceability between code changes and task requirements.

Actions Menu

Quick access to advanced operations:

Share: Generate shareable links to the task. This feature requires a Pro subscription.

History: View the complete workflow log showing all status changes with timestamps and users.

Duplicate: Create a copy of this task with the same content. Choose which fields to copy when creating the duplicate.

Move: Transfer the task to a different project. The task retains its content but adopts the new project's workflows and settings.

Delete: Permanently remove the task. Deletion requires confirmation and appropriate permissions.

AI-Powered Optimization

The AI button in the sidebar header opens optimization suggestions powered by machine learning. This Pro feature analyzes your task description and suggests improvements for clarity, completeness, and actionability.

Keyboard Shortcuts

Navigate the task panel efficiently with keyboard shortcuts:

• Escape: Close the panel
• Tab: Move between editable fields
• Cmd/Ctrl + Enter: Save current field and move to next
• Cmd/Ctrl + S: Save all pending changes

Real-Time Updates

Changes made by other team members appear automatically without refreshing. If someone updates the task status while you are viewing it, the interface reflects the change immediately. This prevents conflicts and keeps everyone working with current information.

Closing the Panel

Close the task panel by:

• Clicking the X button in the header
• Clicking the dimmed area outside the panel
• Pressing the Escape key
• Navigating to a different page

Unsaved changes prompt confirmation before closing to prevent accidental data loss.

Pro Tips

• Quick edits: Double-click any metadata field to jump directly into edit mode
• Keyboard navigation: Use Tab to move through fields without mouse clicks
• Comments for context: Leave comments explaining decisions so future team members understand why choices were made
• Link related tasks: Use subtasks and links to build relationships between work items

How to Report a Problem or Request a Feature

Your feedback matters. Here is how to share it:

If the task panel behaves unexpectedly or you want to suggest improvements to the interface, your input helps us prioritize development.

In the Sidebar, click on Support Tickets and open a ticket for the problem. Everything is interactive and fast through the GitScrum Studio platform.

Kanban Board Views

The Kanban board offers four distinct visualization modes to match different working contexts. Switch between views instantly using the view toggle buttons in the toolbar, giving you the right perspective for planning, execution, or analysis.

The Problem This Solves

A single view cannot serve all needs. During sprint planning, you want to see all tasks in a sortable list. During daily work, you want the classic Kanban column layout. When reviewing progress, you want charts and metrics. Constantly switching between different tools or reports wastes time and loses context.

Multiple integrated views keep all perspectives within the same interface. Your data stays consistent, and switching views takes one click.

What You Are Looking At

The view toggle appears in the board toolbar as a group of four buttons with distinct icons. The currently active view shows with a highlighted state. Click any button to instantly switch to that visualization while maintaining your current filters and board selection.

Kanban View

The default Kanban view displays the classic column-based layout familiar to agile teams worldwide.

Layout: Work items appear as cards organized into vertical columns. Each column represents a workflow stage (Backlog, In Progress, Review, Done, etc.). Columns display horizontally, scrolling left and right as needed.

Features in this view:

• Drag and drop tasks between columns to update status
• Drag columns to reorder workflow stages
• Visual WIP limit indicators on columns
• Task cards with assignees, labels, and progress
• Column task counts in headers
• Quick-access column settings menus

Best for:

• Daily standup discussions
• Real-time work coordination
• Visual workflow management
• Drag-and-drop status updates

Keyboard and mouse: Click a task card to open its detail panel. Drag cards between columns to update workflow status. Hover over column headers to access settings.

List View

The list view presents all tasks in a tabular format optimized for scanning, sorting, and bulk operations.

Layout: Tasks appear as rows in a table with sortable columns. Key information displays inline without opening each task. The view supports pagination for large task sets.

Features in this view:

• Sortable columns for different attributes
• Compact density for seeing more tasks at once
• Quick access to task details
• Pagination for large projects
• Load more functionality for seamless browsing

Best for:

• Sprint planning sessions
• Bulk task review
• Finding specific tasks quickly
• Exporting or reporting needs

Pagination: Large projects paginate automatically. The view shows total task count and current page. Click "Load More" to fetch additional tasks without losing scroll position.

Flow View

The flow view provides analytics visualizations focused on workflow efficiency and throughput patterns.

Layout: Charts and graphs replace the card-based display. The Cumulative Flow Diagram (CFD) shows how work accumulates and moves through stages over time. Additional timeline views provide historical perspective.

Features in this view:

• Cumulative Flow Diagram with workflow breakdown
• Timeline visualization of task movement
• Historical trends for workflow stages
• Interactive chart elements for detailed data

Best for:

• Sprint retrospectives
• Identifying bottlenecks
• Tracking workflow improvements
• Capacity and throughput analysis

Reading the CFD: The Cumulative Flow Diagram stacks workflow stages as colored bands over time. Widening bands indicate work accumulating (potential bottleneck). Parallel bands show steady flow. The vertical distance between bands represents work-in-progress at any point.

Heatmap View

The heatmap view aggregates task activity and distribution into a visual density map, highlighting where work concentrates.

Layout: A grid or radial visualization shows task distribution across dimensions like assignees, time periods, or workflow stages. Color intensity indicates task density or activity level.

Features in this view:

• Visual representation of work distribution
• Activity hotspot identification
• Workload balance visibility
• Team capacity overview

Best for:

• Workload balancing decisions
• Identifying overloaded team members
• Spotting inactive areas
• Resource allocation discussions

Interpreting intensity: Darker or more saturated colors indicate higher task concentration. Use this to identify team members with too much assigned work or workflow stages where tasks accumulate.

Switching Between Views

Click any view button in the toolbar to switch instantly. The view change:

• Preserves your current board selection
• Maintains active filters
• Keeps your position in the project context
• Does not require page reload

You can switch views as often as needed during a work session. Each view loads data appropriate to its visualization needs.

View-Specific Filters

Some filters affect all views equally, while others have view-specific behavior:

Board selection: Affects all views. Changing boards refreshes all views with the new board's data.

Archived toggle: Shows or hides archived tasks across all views.

Search and filters: Applied consistently across views, though display varies by view type.

Performance Considerations

Different views have different data requirements:

Kanban view: Loads visible columns and task cards. Efficient for most project sizes.

List view: Paginates large datasets. Initial load is fast; additional pages load on demand.

Flow view: Requires historical data aggregation. May take longer to load for projects with extensive history.

Heatmap view: Aggregates current state data. Performance depends on task count and analysis timeframe.

Pro Tips

• View for the task: Use Kanban for quick status updates, List for finding specific tasks, Flow for retrospectives, and Heatmap for planning
• Keyboard shortcuts: Learn any view-switching shortcuts to move between perspectives without mouse navigation
• Consistent filtering: Apply filters in one view, then switch views to see the same filtered set from different angles
• Presentation mode: Flow and Heatmap views work well for team meetings and stakeholder updates

How to Report a Problem or Request a Feature

Your feedback matters. Here is how to share it:

If view switching behaves unexpectedly or you want additional visualization options, your input helps prioritize development.

In the Sidebar, click on Support Tickets and open a ticket for the problem. Everything is interactive and fast through the GitScrum Studio platform.

WIP Limits

Work-in-Progress (WIP) limits constrain how many tasks can exist in a column simultaneously. This Kanban practice prevents overloading any stage of your workflow and encourages teams to finish work before starting new tasks.

The Problem This Solves

Without limits, teams tend to start more work than they can finish. Tasks pile up in progress columns, context switching increases, and nothing gets done quickly. This pattern creates the illusion of productivity (lots of tasks started) while actually slowing delivery (few tasks completed).

WIP limits create a forcing function. When a column reaches its limit, you cannot add more tasks until something moves forward. This surfaces bottlenecks immediately and naturally encourages team members to help clear blockages instead of starting new work.

What You Are Looking At

The WIP Limit modal appears when you select "WIP Limit" from a column's dropdown menu. The modal shows the current column name for reference, a slider to set the numeric limit, and a checkbox to disable limits entirely.

Opening WIP Limit Settings

To configure WIP limits for a column:

1. Navigate to your Kanban board
2. Click the three-dot menu icon in the target column header
3. Select "WIP Limit" from the dropdown menu

You need board management permissions to modify WIP limits. If this option does not appear, contact your workspace administrator.

Setting a WIP Limit

The slider control adjusts the maximum number of tasks allowed in the column. Move the slider to set a value between 1 and 15. The current limit displays below the slider as you adjust it.

Choosing the right limit:

• Start with your team size for in-progress columns (if 3 developers work on tasks, limit to 3-4)
• Allow slightly higher limits for queue columns where work waits
• Set lower limits for bottleneck stages you want to improve
• Consider task complexity: complex tasks need lower limits per person

The limit takes effect immediately when you close the modal. No separate save action is required since the value updates as you adjust the slider.

The No WIP Checkbox

Enable the "No WIP" checkbox to remove all limits from a column. This effectively sets the limit to 0, which the system interprets as unlimited.

Some columns genuinely need unlimited capacity:

• Backlog columns where all future work queues
• Done columns where completed work accumulates
• Archive columns for historical records

Enable this option sparingly. Unlimited in-progress columns defeat the purpose of Kanban's flow optimization.

How WIP Limits Work

When a column has a WIP limit:

Adding tasks: Attempts to drag a task into a column at capacity trigger a warning modal. The system explains the limit and prevents the action. To add the task, first move something else out of the column.

Moving tasks out: Moving tasks out of a column that was at capacity immediately makes room for new work. No additional action is required.

Column counter: The task count badge in the column header helps monitor capacity. Some teams configure visual warnings when columns approach their limits.

Creating tasks: Creating a new task assigned to a column at capacity may trigger the same limit warning, depending on your project's task creation configuration.

The WIP Limit Warning Modal

When you attempt to exceed a WIP limit, a modal appears explaining:

• The column has reached its WIP limit
• You cannot add more tasks
• What action to take (remove tasks from the column first)

This is not an error. The system is working correctly to enforce flow constraints. Review the column and determine what can move forward or what blocking issue needs resolution.

Benefits of WIP Limits

Reduced multitasking: Developers focus on fewer items at once, improving quality and completion speed.

Exposed bottlenecks: When work piles up behind a limited column, you see exactly where the process struggles. This visibility drives process improvement.

Faster flow: Counterintuitively, limiting work-in-progress speeds up delivery. Less concurrent work means less context switching and faster individual task completion.

Better forecasting: With stable WIP, throughput becomes predictable. You can confidently estimate when work will complete based on historical data.

Team collaboration: When developers cannot start new work due to limits, they naturally help colleagues clear bottlenecks. This builds team cohesion.

Recommended Limits by Column Type

Backlog / To Do: No limit (work queues here)

Ready for Development: Team size times 2 (buffer for planning)

In Development: Team size (one task per active developer)

Code Review: Team size divided by 2 (reviews happen between coding sessions)

Testing / QA: Team size (one item per tester or shared testing capacity)

Done: No limit (completed work accumulates)

These recommendations provide starting points. Adjust based on your actual flow patterns and cycle time data.

Monitoring WIP Effectiveness

After implementing limits, monitor your Cumulative Flow Diagram (available in the Flow view) to observe:

Stable bands: Work-in-progress counts stabilize instead of growing unbounded.

Smooth flow: Tasks move steadily from left to right without large accumulations.

Quick bottleneck identification: Columns that consistently hit limits while downstream columns empty indicate process constraints to address.

Adjusting Limits Over Time

WIP limits are not permanent. Review and adjust based on:

• Team size changes
• Project complexity variations
• Observed bottleneck patterns
• Cycle time trends

Start conservative (lower limits) and increase gradually if work flows smoothly without blocking. The goal is sustainable flow, not maximum utilization.

Pro Tips

• Limit the limits: Not every column needs a limit. Focus on in-progress stages where work actively happens
• Make limits visible: Consider adding the limit number to column names during adoption (e.g., "In Progress [3]")
• Team discussion: When limits block work, use it as a conversation starter about why flow is impeded
• Emergency override: Occasionally business needs require exceeding limits. Discuss as a team, make exceptions explicit, and return to normal limits quickly

How to Report a Problem or Request a Feature

Your feedback matters. Here is how to share it:

If WIP limit warnings appear incorrectly or you want additional limit configuration options, we value your input.

In the Sidebar, click on Support Tickets and open a ticket for the problem. Everything is interactive and fast through the GitScrum Studio platform.