Skip to content

fix: label document notifications and activities - #169

Open
lollipop-onl wants to merge 3 commits into
mainfrom
lollipop-onl/fix-document-labels
Open

lollipop-onl wants to merge 3 commits into
mainfrom
lollipop-onl/fix-document-labels

Conversation

@lollipop-onl

@lollipop-onl lollipop-onl commented Sep 28, 2026 •

Copy link
Copy Markdown
Collaborator

Summary

Fixes the notification reason and activity type labels for Backlog's document feature.

  • Notification reasons: 14, 15 and 17 were mapped to mention reasons the API no longer defines, so bee notification list showed the wrong reason for every document notification. They now read Document commented / Document comment replied / Document mentioned. 16 and 18 (issues bulk-added, assigned / notified) are added.
  • Activity types: 36–46, 48 and 49 (document events) and 50 / 51 (related issue added / removed) are added. bee project activities, bee space activities and bee user activities showed Type N for them.

The labels follow the Japanese API reference, which lists reasons 16 and 18 that the English page omits. 50 and 51 are not in the public reference yet, but the activity endpoints return them. All values, including 34, 35 and 47 (not in the public reference either), were cross-checked against Backlog's internal definitions.

Document activities also get a summary now: getActivitySummary falls back to title (and documents[].title for bulk creation). Before, they showed an empty SUMMARY column once labelled.

Test plan

  • vp check passes
  • vp test: all tests pass
  • Live space: notifications with reasons 15–18 carry what the labels say (15/17 have document, 16/18 have neither issue nor document); bee project activities shows Document Created <title> and Related Issue Added

🤖 Generated with Claude Code

Backlog reuses notification reasons 14-18 and adds activity types 36-49 for
the document feature, but bee still mapped 14-17 to mention reasons that
the API no longer defines. `bee notification list` therefore showed the
wrong reason for every document notification, and the activity commands
fell back to "Type N" for document events.

The labels follow the Japanese API reference, which also lists reasons 16
and 18 (bulk-added issues) that the English page omits. Types 34, 35 and
47 are kept even though neither page lists them, since they come back in
real activity data.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@lollipop-onl lollipop-onl added the bug Something isn't working label Sep 28, 2026
@lollipop-onl lollipop-onl self-assigned this Sep 28, 2026
@github-actions

github-actions Bot commented Sep 28, 2026 •

Copy link
Copy Markdown

Coverage Report

Status Category Percentage Covered / Total
🔵 Lines 92.74% 1944 / 2096
🔵 Statements 92.96% 2034 / 2188
🔵 Functions 92.87% 456 / 491
🔵 Branches 80.68% 848 / 1051
File Coverage
File Stmts Branches Functions Lines Uncovered Lines
Changed Files
packages/backlog-utils/src/activity-labels.ts 100% 100% 100% 100%
packages/backlog-utils/src/activity-summary.ts 83.33% 66.66% 66.66% 82.35% 14, 26-27
packages/backlog-utils/src/notification-reason-labels.ts 100% 100% 100% 100%
Generated in workflow #540 for commit 16ae567 by the Vitest Coverage Report Action

lollipop-onl and others added 2 commits September 29, 2026 02:19
Backlog's internal ActivityType also defines 50 and 51 for adding and
removing related issues, and the API returns them from the activity
endpoints, but the public API reference does not list them yet, so they
still showed as "Type 50" / "Type 51".

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
With the document activity types labelled, `bee project activities` and
friends showed "Document Created" next to an empty summary, because
getActivitySummary only knew issue-shaped content. Document activities
carry `title` (or `documents[].title` for bulk creation), which a live
space confirmed.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant