Skip to content

feat(TAP-13052): §4.1 navigation, alarm events and notification records - #658

Draft
weiliang110100 wants to merge 10 commits into
developfrom
hardy/TAP-13052-6ad1cd94
Draft

weiliang110100 wants to merge 10 commits into
developfrom
hardy/TAP-13052-6ad1cd94

Conversation

@weiliang110100

@weiliang110100 weiliang110100 commented Oct 16, 2026 •

Copy link
Copy Markdown
Contributor

TAP-13052 P0:§4.1 导航、告警事件与通知记录

Jira:https://tapdata.atlassian.net/browse/TAP-13052

变更

  • 主菜单:运维中心 › 告警事件;消息与通知 › 通知记录 / 通知设置;系统管理 › 操作审计。旧 /notification/* 路由重定向(保留原路由名),移除 NotifyLayout。
  • 铃铛弹层:未读站内告警通知(最多 10 条,角标 99+),管理员许可证提醒,点击即标为已读并打开详情,全部标为已读前展示影响条数。
  • 告警事件页:统计卡、URL 同步筛选、发生次数、对象类型、通知结果、详情抽屉,关闭说明“不代表问题已恢复”。
  • 通知记录页:按告警聚合、全部/未读/发送失败页签、筛选、批次与收件人投递明细、单条/批量已读未读。
  • 通知渠道只保留站内消息与邮件(企业版告警通知渠道;短信、微信仅云版,暂不考虑)。
  • 通知设置页:隐藏已下线的站内通知开关,提示前往告警设置。
  • 关联告警事件已被清除(历史版本任务重新运行时删除)的通知:列表提示,详情禁用「查看告警事件」并说明原因;告警事件详情显示“任务重新运行时归档”;两个详情抽屉的告警类型显示为可读名称。
  • 文案:渠道「站内」改为「站内消息」,「投递结果/状态/明细」改为「发送结果/状态/明细」,结果标签悬停说明“成功数/收件人数”。
  • 权限:告警事件、通知记录、操作审计路由配置 v2_alarm_event / v2_notification_record / v2_audit_log(菜单与路由守卫自动生效);关闭按钮需要 v2_alarm_event_ack_close 并改调 POST /api/alarms/close;铃铛「查看全部」、详情中跳转告警事件/通知记录按目标权限显示;他人通知不显示未读、不可标记,详情提示阅读状态不受影响。
  • 角色权限页(固定模块树)增加「运维中心 › 告警事件(功能权限:关闭)」「消息与通知 › 通知记录」,「系统管理」下增加「操作审计」。
  • 中文简体/繁体/英文文案。

验证

  • 已合入最新 develop;pnpm build:daas 通过;改动文件 eslint 无新增问题(i18n 文件中 default export 与重复键为既有问题)。
  • 需配合 tapdata、tapdata-enterprise 同名分支后端联调,手工验收步骤见 Jira。

🤖 Generated with Claude Code

- Main menu: Operations > Alarm Events, Messages & Notifications >
  Notification Records / Settings, System > Operation Audit; old
  /notification/* routes redirect, NotifyLayout removed
- Bell popover: unread in-app alarm notifications (99+), license reminder
  for admins, open-to-read, mark-all-read with scope confirmation
- Alarm events: stats cards, URL-synced filters, occurrence count, object
  type, delivery result, detail drawer, close hint
- Notification records: aggregated by alarm event, All/Unread/Failed tabs,
  filters, batch/recipient delivery details, single/batch read & unread
- Notification setting: in-app toggles retired, link to alarm settings
- zh-CN / zh-TW / en texts

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@weiliang110100
weiliang110100 requested a review from feynmx October 16, 2026 09:04
weiliang110100 and others added 9 commits October 20, 2026 09:16
…cation views

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

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…rds and operation audit

Routes carry v2_alarm_event / v2_notification_record / v2_audit_log_list,
the close action needs v2_alarm_event_ack_close and uses /api/alarms/close,
cross-module links follow the target permission, and other users'
notifications show no unread state and cannot be marked.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…n role permissions

The role editor renders a fixed module tree, so add v2_ops-center
(alarm events with the close button), v2_message-center (notification
records) and v2_audit_log under system management.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The enterprise edition sends alarm notifications through in-app messages
and email only; SMS and WeChat are cloud-only, so drop them from the
channel filter and labels.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@weiliang110100
weiliang110100 marked this pull request as ready for review October 21, 2026 02:26
@weiliang110100
weiliang110100 marked this pull request as draft October 21, 2026 03:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant