​

Flashduty Terminology Glossary

Chinese-English terminology mapping. Maintain consistency during translation.

​

Core Concepts

​

Incident Management

​

Alert Processing

​

Schedule & On-call

​

Severity Levels

​

Incident Status

​

Time & Notifications

​

Subscription & Plans

​

Account & Team

​

UI & Labels

​

Actions

​

Third-party Integrations

​

Technical Terms

​

Regional

​

API documentation

Used by the api-review skill when generating api-reference/openapi.{en,zh}.json. Stay consistent with these terms across operation summaries, descriptions, and field labels so the reference reads uniformly.

​

Operation verbs (summary prefix)

​

Reference / structural terms

​

Permission class names

Permission classes come from fc-pgy/logic/permission/permission_test.go — use the classEn field there as the authoritative English label. Common ones: When a permission’s classEn is set in permission_test.go, trust it over any guess. The Flashduty product team manages those labels and keeps them consistent with the console UI.

​

Notes for the generator

• Prefer frontend labels over translation. If the frontend console uses a specific English label for a concept (e.g., “Notification template” vs “Message template”), use the frontend label. Check fc-foundation-app/src/Packages/saas/pages/... i18n files as the source of truth for user-facing labels.
• Don’t translate product names. “On-call”, “RUM”, “Monitors”, “Flashduty” stay English in both languages.
• Don’t translate wire values. Enum values like "enabled", "InvalidParameter", "updated_at" are wire-format identifiers and must appear identically in both EN and ZH specs. Only their descriptions get localized.
• Verb tense — English uses imperative (“Create a template”, “Delete an incident”), Chinese uses short noun phrases (“创建模板”, “删除故障”). Don’t prefix Chinese summaries with verbs like “创建一个” when “创建” alone reads naturally.