Back to Details

linear-usage

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Linear & Issue Tracking Best Practices

Linear 与问题跟踪最佳实践

Issue Writing Guidelines

问题撰写指南

Clear Titles

清晰的标题

Write titles that describe the problem or outcome:
  • Good: "Users can't reset password on mobile Safari"
  • Bad: "Password bug"
  • Good: "Add export to CSV for user reports"
  • Bad: "Export feature"
撰写能描述问题或预期结果的标题：
  • 优秀示例： "用户无法在移动版Safari中重置密码"
  • 糟糕示例： "密码bug"
  • 优秀示例： "为用户报告添加导出为CSV功能"
  • 糟糕示例： "导出功能"

Effective Descriptions

有效的描述

Include:
  1. Context: Why this matters
  2. Current behavior: What happens now (for bugs)
  3. Expected behavior: What should happen
  4. Steps to reproduce: For bugs
  5. Acceptance criteria: Definition of done
需包含以下内容：
  1. 背景： 该问题的重要性
  2. 当前行为： 当前发生的情况（针对bug）
  3. 预期行为： 应该发生的情况
  4. 复现步骤： 针对bug
  5. 验收标准： 完成定义

Templates

模板

Bug report:
undefined
Bug报告：
undefined

Description

Description

Brief description of the issue.
Brief description of the issue.

Steps to Reproduce

Steps to Reproduce

  1. Step one
  2. Step two
  3. Issue occurs
  1. Step one
  2. Step two
  3. Issue occurs

Expected Behavior

Expected Behavior

What should happen.
What should happen.

Actual Behavior

Actual Behavior

What happens instead.
What happens instead.

Environment

Environment

  • Browser/OS
  • User type

**Feature request:**
  • Browser/OS
  • User type

**功能请求：**

Problem Statement

Problem Statement

What problem does this solve?
What problem does this solve?

Proposed Solution

Proposed Solution

High-level approach.
High-level approach.

Acceptance Criteria

Acceptance Criteria

  • Criterion 1
  • Criterion 2
undefined
  • Criterion 1
  • Criterion 2
undefined

Label Taxonomy

标签分类体系

Recommended Labels

推荐标签

Type labels:
  • bug
    - Something isn't working
  • feature
    - New functionality
  • improvement
    - Enhancement to existing feature
  • chore
    - Maintenance, refactoring
Area labels:
  • frontend
    , 
    backend
    , 
    api
    , 
    mobile
  • Or by feature area: 
    auth
    , 
    payments
    , 
    onboarding
Status labels (if not using workflow states):
  • needs-triage
    , 
    blocked
    , 
    needs-design
类型标签：
  • bug
    - 功能异常
  • feature
    - 新功能
  • improvement
    - 现有功能增强
  • chore
    - 维护、重构
领域标签：
  • frontend
    , 
    backend
    , 
    api
    , 
    mobile
  • 或按功能领域划分：
    auth
    , 
    payments
    , 
    onboarding
状态标签（未使用工作流状态时）：
  • needs-triage
    , 
    blocked
    , 
    needs-design

Label Best Practices

标签最佳实践

  • Keep label count manageable (15-25 total)
  • Use consistent naming convention
  • Color-code by category
  • Review and prune quarterly
  • 控制标签数量（总计15-25个）
  • 使用统一的命名规范
  • 按类别添加颜色标识
  • 每季度审核并清理标签

Priority and Estimation

优先级与估算

Priority Levels

优先级等级

  • Urgent (P0): Production down, security issue
  • High (P1): Major functionality broken, key deadline
  • Medium (P2): Important but not urgent
  • Low (P3): Nice to have, minor improvements
  • 紧急（P0）： 生产环境故障、安全问题
  • 高（P1）： 核心功能故障、关键截止日期
  • 中（P2）： 重要但不紧急
  • 低（P3）： 锦上添花的功能、小改进

Estimation Tips

估算技巧

  • Use relative sizing (points) not hours
  • Estimate complexity, not time
  • Include testing and review time
  • Re-estimate if scope changes significantly
  • 使用相对规模（点数）而非小时数
  • 估算复杂度，而非时间
  • 包含测试与评审时间
  • 若范围发生重大变化，重新估算

Cycle/Sprint Planning

迭代周期规划

Cycle Best Practices

迭代最佳实践

  • Duration: 1-2 weeks typically
  • Capacity: Plan for 70-80% to allow for interrupts
  • Carryover: Review why items didn't complete
  • Retrospective: Brief review at cycle end
  • 时长： 通常1-2周
  • 容量： 按70-80%规划，预留处理突发情况的时间
  • 遗留事项： 复盘未完成项的原因
  • 回顾会议： 迭代结束后进行简短回顾

Planning Process

规划流程

  1. Review backlog priorities
  2. Pull issues into cycle
  3. Break down large items (>5 points)
  4. Assign owners
  5. Identify dependencies and blockers
  1. 梳理待办事项优先级
  2. 将问题拉入迭代周期
  3. 拆分大型任务（>5点）
  4. 分配负责人
  5. 识别依赖项与阻塞点

Project Organization

项目组织

Projects vs Initiatives

项目与举措

Projects: Focused, time-bound work (1-3 months)
  • Single team typically
  • Clear deliverable
  • Example: "Mobile app v2 launch"
Initiatives: Strategic themes
  • May span multiple projects
  • Longer-term goals
  • Example: "Platform reliability"
项目： 聚焦、有时间限制的工作（1-3个月）
  • 通常由单个团队负责
  • 明确的交付成果
  • 示例："移动应用v2版本发布"
举措： 战略主题
  • 可能涵盖多个项目
  • 长期目标
  • 示例："平台可靠性提升"

Roadmap Tips

路线图技巧

  • Keep roadmap items high-level
  • Update status regularly
  • Link to detailed issues/projects
  • Share with stakeholders
  • 路线图项保持高粒度
  • 定期更新状态
  • 关联至详细的问题/项目
  • 与利益相关者共享

Triage Workflows

问题分流工作流

Triage Process

分流流程

  1. Review new issues daily
  2. Add missing information (labels, priority)
  3. Assign to appropriate team/person
  4. Link related issues
  5. Move to backlog or close if invalid
  1. 每日审核新问题
  2. 补充缺失信息（标签、优先级）
  3. 分配至对应团队/人员
  4. 关联相关问题
  5. 移入待办事项或标记为无效关闭

Closing Issues

关闭问题

Close with clear reason:
  • Completed: Work is done
  • Duplicate: Link to original
  • Won't fix: Explain why
  • Invalid: Missing info, not reproducible
关闭时需说明清晰原因：
  • 已完成： 工作已完成
  • 重复： 关联至原始问题
  • 不会修复： 说明原因
  • 无效： 信息缺失、无法复现

GitHub Integration

GitHub集成

Linking PRs to Issues

将PR关联至问题

  • Reference Linear issue ID in PR title or description
  • Linear auto-links and updates status
  • Use branch names with issue ID for automatic linking
  • 在PR标题或描述中引用Linear问题ID
  • Linear会自动关联并更新状态
  • 使用包含问题ID的分支名称以实现自动关联

Workflow Automation

工作流自动化

  • PR opened → Issue moves to "In Progress"
  • PR merged → Issue moves to "Done"
  • Configure in Linear settings
  • PR创建 → 问题状态变为"进行中"
  • PR合并 → 问题状态变为"已完成"
  • 在Linear设置中配置该规则