spark-recipe-shared-inbox-status

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Recipe: Shared Inbox Status

方案:共享收件箱状态

Review the health of one or more shared inboxes - open items, completed work, unassigned emails, and how assignments are distributed across team members.
Prerequisite: Read the
use-spark
base skill for command reference and filter syntax.
Access level required: read-only.
查看一个或多个共享收件箱的健康状况——已打开项目、已完成工作、未分配邮件,以及任务在团队成员间的分配情况。
前提条件: 阅读
use-spark
基础技能文档以获取命令参考和筛选语法。
所需访问权限: 只读。

Steps

步骤

Step 1: Discover shared inboxes

步骤1:发现共享收件箱

bash
spark accounts
Note each shared inbox address and the team it belongs to.
bash
spark accounts
记录每个共享收件箱的地址及其所属团队。

Step 2: Check open items

步骤2:检查已打开项目

For each shared inbox:
bash
spark emails shared@co.com:Inbox --filter "is:shared_inbox_open"
These are active items that still need attention.
针对每个共享收件箱执行:
bash
spark emails shared@co.com:Inbox --filter "is:shared_inbox_open"
这些是仍需处理的活跃项目。

Step 3: Check unassigned items

步骤3:检查未分配项目

bash
spark emails shared@co.com:Inbox --filter "assigned_to:unassigned"
Unassigned items are falling through the cracks - no one owns them yet.
bash
spark emails shared@co.com:Inbox --filter "assigned_to:unassigned"
未分配项目属于遗漏的工作——目前还没有负责人。

Step 4: Review per-member assignments

步骤4:查看按成员划分的任务分配

bash
spark team "Team Name"
The assignment summary shows how work is distributed. For a deeper look at a specific member's load:
bash
spark emails shared@co.com:Inbox --filter "assigned_to:alice@co.com"
spark emails shared@co.com:Inbox --filter "assigned_to:bob@co.com"
bash
spark team "Team Name"
任务分配摘要会展示工作的分布情况。如需深入查看特定成员的工作负载:
bash
spark emails shared@co.com:Inbox --filter "assigned_to:alice@co.com"
spark emails shared@co.com:Inbox --filter "assigned_to:bob@co.com"

Step 5: Check completed items

步骤5:检查已完成项目

bash
spark emails shared@co.com:Inbox --filter "is:shared_inbox_done"
Review recently completed items for a sense of throughput.
bash
spark emails shared@co.com:Inbox --filter "is:shared_inbox_done"
查看近期已完成的项目以了解工作处理量。

Step 6: Present the status

步骤6:呈现状态报告

Report per shared inbox:
  • Open: N items awaiting action
  • Unassigned: M items with no owner
  • Per member: assignment counts (flag anyone with significantly more or fewer)
  • Done: K items completed recently
If there are multiple shared inboxes, present each separately, then a combined summary.
针对每个共享收件箱提交报告:
  • 已打开: N个待处理项目
  • 未分配: M个无负责人的项目
  • 按成员划分: 任务分配数量(标记任务量明显过多或过少的成员)
  • 已完成: K个近期完成的项目
如果存在多个共享收件箱,请分别呈现每个收件箱的报告,再提供合并后的汇总。

Tips

小贴士

  • Run this daily for active shared inboxes, weekly for quieter ones.
  • Unassigned items are the most actionable finding - they represent work that nobody is looking at.
  • Combine per-member counts with
    recipe-team-workload
    for a fuller picture of who has bandwidth.
  • If a shared inbox has high open count but low unassigned count, work is distributed but not being closed - look for stale assignments.
  • Use
    spark thread <id>
    to read any item that looks stale or unusual.
  • For teams with multiple shared inboxes, the total unassigned count across all inboxes is the key metric.
  • 对于活跃的共享收件箱,每日执行此操作;对于使用频率较低的收件箱,每周执行一次即可。
  • 未分配项目是最需要处理的发现——它们代表着无人关注的工作。
  • 将按成员划分的任务数量与
    recipe-team-workload
    结合使用,以更全面地了解团队成员的可用带宽。
  • 如果某个共享收件箱的已打开项目数量较多但未分配项目数量较少,说明工作已分配但未完成——需检查是否存在停滞的任务。
  • 使用
    spark thread <id>
    查看任何看起来停滞或异常的项目。
  • 对于拥有多个共享收件箱的团队,所有收件箱的未分配项目总数是关键指标。