Skip to main content

Agile Project Management

iForge has a built-in complete Scrum agile project management module, with the core feature being deep integration of tasks and code.

Hierarchy​

Project
  └── Epic
       └── User Story
            └── Task
                 ├── Status
                 ├── Priority
                 ├── Assignee
                 ├── Sprint
                 └── Branch ← Tasks are directly associated with Git branches

🔗 Task-Code Integration (Core Feature)​

This is the core feature that distinguishes iForge from other Git platforms—making project management and code development no longer two separate systems.

Branch as Task​

One-click create development branches from task cards, branch names automatically include task numbers:

# Create branch from task TASK-12
git checkout -b task-12-fix-login-bug

Commit as Record​

Reference task numbers in commit messages, automatically associate with task timeline:

git commit -m "Fix login issue #TASK-12"
git commit -m "Add unit tests #TASK-12 #TASK-15"

After committing, the task details page automatically displays associated commit records, achieving code changes traceable to business requirements.

MR as Delivery​

When creating merge requests, tasks can be associated, and task status is automatically updated after merging:

  1. Create MR from task, source branch is automatically populated
  2. Reference task number in MR description
  3. Task status automatically transitions to "Completed" after merge

Bidirectional Traceability​

  • View code from task: Task details page shows associated branches, commits, MRs
  • View task from code: Click task number in commit history to jump to task details

Task-Driven Development Workflow​

The following is a typical development workflow example:

┌─────────────────────────────────────────────────────────────────┐
│  1. Product manager creates requirements on the board,          │
│     breaks them down into Stories and Tasks                     │
│     └── TASK-12: Fix user login timeout issue                   │
│                                                                   │
│  2. Developer creates development branch from task card          │
│     └── task-12-fix-login-timeout                                 │
│                                                                   │
│  3. After development, commit code, reference task number        │
│     └── git commit -m "Optimize database queries #TASK-12"       │
│                                                                   │
│  4. Create merge request, automatically associate with task      │
│     └── MR-45: Fix login timeout → associate TASK-12            │
│                                                                   │
│  5. Code review passed, task status automatically updated        │
│     after merge                                                  │
│     └── TASK-12 status: In Progress → Completed                  │
└─────────────────────────────────────────────────────────────────┘

Actual Operation Steps​

  1. Create Task: Create Task in project board, set title, description, priority, assignee
  2. Create Branch: Click "Create Branch" from task card, system automatically generates task-{id}-{slug} format branch name
  3. Develop and Commit: Reference task number #TASK-12 in commit messages during local development
  4. Create MR: Create merge request after pushing branch, system automatically associates task
  5. Merge Complete: After code review passes and merge, task status automatically updates to "Completed"

Sprint Management​

  • Create Sprint, set start and end dates
  • Sprint workflow progress: Requirements → Break down tasks → Plan Sprint → Assign assignees → Start development → Review → Complete
  • Sprint board: Visual management of task status transitions
  • Backlog: Requirements pool for managing unplanned tasks

Task Board​

  • Drag-and-drop kanban board, custom columns (statuses)
  • Inline editing: High-frequency fields (status, priority, assignee) can be edited directly in the list
  • Color coding: Status dots + priority group color schemes
  • Subtask support: Tasks can be broken down into subtasks, showing completion progress

Task Dependencies​

Supports directed dependencies between tasks:

  • Predecessor tasks: Mark task B depends on task A
  • Dependency types: Support "Finish-to-Start" (FS) and other dependency types
  • Visualization: Display dependencies on the board to avoid blocking

Time Tracking​

  • Work logs: Record time spent on each task
  • Statistical reports: Summarize workload by user, time period
  • Estimated hours: Set estimated hours when creating tasks

AI Assistance​

  • AI optimizes task titles and descriptions
  • AI analyzes requirements and breaks down tasks
  • Supports multiple AI model configurations (OpenAI, DeepSeek, Qwen, etc.)

Custom Status​

  • Custom task status workflow
  • Configure status transition rules (which statuses can transition to which)
  • Support "Completed" status to automatically close tasks