@checkstack/incident-frontend 0.7.1 → 0.8.1

package/CHANGELOG.md

@@ -1,5 +1,133 @@
 # @checkstack/incident-frontend
 
+## 0.8.1
+
+### Patch Changes
+
+- Updated dependencies [9016526]
+  - @checkstack/common@0.10.0
+  - @checkstack/catalog-common@2.2.0
+  - @checkstack/incident-common@1.2.0
+  - @checkstack/notification-common@1.1.0
+  - @checkstack/auth-frontend@0.6.1
+  - @checkstack/dashboard-frontend@0.7.1
+  - @checkstack/frontend-api@0.5.1
+  - @checkstack/notification-frontend@0.4.1
+  - @checkstack/tips-frontend@0.2.1
+  - @checkstack/ui@1.8.1
+  - @checkstack/signal-frontend@0.1.3
+
+## 0.8.0
+
+### Minor Changes
+
+- 1ef2e79: feat: hotlinks on incidents/maintenances and additional links on systems
+
+  Users with `manage` access on an incident, maintenance, or system can now
+  attach free-form URL "hotlinks" — Jira tickets, runbooks, dashboards, ticket
+  tools, etc. — alongside the existing fields.
+
+  - **Incidents** & **maintenances**: links live on the entity itself and are
+    surfaced both in the editor dialog and on the public detail page. Two new
+    RPC procedures per plugin (`addLink`, `removeLink`) gated behind the
+    existing `manage` access rule. Links are returned as part of
+    `getIncident` / `getMaintenance` and cache-invalidated on every link
+    mutation.
+  - **Systems**: a parallel `system_links` table with `getSystemLinks`,
+    `addSystemLink`, `removeSystemLink` procedures. Surfaced inside the
+    system editor (next to contacts) and on the read-only system detail
+    sidebar. Cache-scoped per-system so list endpoints remain hot.
+  - **Shared UI**: a `LinksEditor` component in `@checkstack/ui` does the
+    presentation; the three plugins each own their own RPC wiring.
+
+  Database changes ship as additive migrations (new `incident_links`,
+  `maintenance_links`, `system_links` tables, all FK-cascaded on parent
+  delete). No existing columns or rows are touched.
+
+  The system incident and maintenance history pages now sort by relevance:
+  active entries (non-`resolved` incidents, `scheduled` or `in_progress`
+  maintenances) appear at the top, with creation date descending as the
+  tiebreaker.
+
+- 3547670: Wire the new tips infrastructure across the frontends:
+
+  **Empty-state coaching.** Replace generic "no items" copy with onboarding
+  guidance — short description, three numbered steps and a primary CTA — on
+  every EmptyState that has a meaningful next action. Affects: catalog
+  (systems + groups), dashboard, health-check page, integrations (subscriptions
+
+  - provider connections), GitOps providers + secrets, GitOps provenance,
+    SLO config + overview, maintenance config, satellites, plugin manager,
+    incident config, announcements. Read-only EmptyStates (incident history,
+    maintenance history, plugin events) get clearer descriptions explaining
+    what would populate them.
+
+  **First-run anchored tips.** Add `<Tip>` popovers to the most important
+  "Create" affordances so first-time users see a one-line explanation of
+  what they're about to make and why it matters: catalog “Add System” /
+  “Add Group”, healthcheck “Create Check”, integrations “New Subscription”,
+  GitOps “Add Provider”, SLO “Create SLO”, maintenance “Create Maintenance”,
+  satellite “Create Satellite”, plugin-manager “Install plugin”, incident
+  “Report Incident”, announcement “New Announcement”. Each tip is dismissed
+  per user (server-backed when signed in, localStorage otherwise) and
+  namespaced through `qualifyTipId(plugin, …)` so it cannot escape the
+  plugin's own namespace.
+
+  **Welcome banner on the dashboard.** A `<TipBanner>` at the top of the
+  dashboard introduces Checkstack's main flow ("add a system, then a health
+  check") with a one-click jump into the catalog.
+
+### Patch Changes
+
+- 950d6ec: Fix mobile UserMenu items rendering at zero height, group menu items by
+  section, and unstack cramped card headers on small viewports.
+
+  - **UserMenu mobile bug**: On mobile, the user-menu Sheet rendered every
+    menu item as a grid row, which combined with `flex-shrink: 1` on each
+    item collapsed the buttons whose internal layout uses `display: flex`
+    (the items registered with `useNavigate` rather than `<Link>`) to zero
+    content height. Switched the mobile container to a flex column with
+    `[&>*]:shrink-0` and added `min-h-0` so the sheet scrolls correctly
+    when the list overflows.
+
+  - **UserMenu grouping**: Slot extensions now accept an optional `group`
+    field. The user menu buckets `UserMenuItemsSlot` extensions by `group`
+    and renders each group under a labeled header (`Workspace`,
+    `Reliability`, `Configuration`, `Documentation`, `Account`). Existing
+    core plugins are tagged with the appropriate group; third-party plugins
+    can pick any of these or supply their own label. Untagged extensions
+    render last with no header. `UserMenuItemsBottomSlot` is unaffected.
+
+  - **Card header responsiveness**: `CardHeaderRow` (the primitive shared by
+    Incident, Maintenance, Auth, Catalog, GitOps and other config cards) now
+    stacks vertically on narrow viewports and only switches to a single row
+    at the `sm` breakpoint, so titles and adjacent filter controls (e.g.
+    status `Select`, "Show resolved" checkbox) no longer cram together on
+    mobile. Refactored the Incident and Maintenance config pages to use the
+    primitive instead of a hand-rolled `flex items-center justify-between`
+    row, and made their `Select` triggers full-width on mobile.
+
+- Updated dependencies [42abfff]
+- Updated dependencies [3547670]
+- Updated dependencies [1ef2e79]
+- Updated dependencies [aa89bc5]
+- Updated dependencies [3547670]
+- Updated dependencies [3547670]
+- Updated dependencies [950d6ec]
+- Updated dependencies [3547670]
+- Updated dependencies [3547670]
+  - @checkstack/common@0.9.0
+  - @checkstack/ui@1.8.0
+  - @checkstack/incident-common@1.1.0
+  - @checkstack/catalog-common@2.1.0
+  - @checkstack/frontend-api@0.5.0
+  - @checkstack/notification-frontend@0.4.0
+  - @checkstack/tips-frontend@0.2.0
+  - @checkstack/auth-frontend@0.6.0
+  - @checkstack/dashboard-frontend@0.7.0
+  - @checkstack/notification-common@1.0.2
+  - @checkstack/signal-frontend@0.1.2
+
 ## 0.7.1
 
 ### Patch Changes

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@checkstack/incident-frontend",
-  "version": "0.7.1",
+  "version": "0.8.1",
   "license": "Elastic-2.0",
   "type": "module",
   "main": "src/index.tsx",
@@ -13,16 +13,17 @@
     "lint:code": "eslint . --max-warnings 0"
   },
   "dependencies": {
-    "@checkstack/auth-frontend": "0.5.32",
-    "@checkstack/catalog-common": "2.0.0",
-    "@checkstack/common": "0.7.0",
-    "@checkstack/dashboard-frontend": "0.6.0",
-    "@checkstack/frontend-api": "0.4.1",
-    "@checkstack/incident-common": "1.0.0",
-    "@checkstack/notification-common": "1.0.0",
-    "@checkstack/notification-frontend": "0.3.0",
-    "@checkstack/signal-frontend": "0.1.0",
-    "@checkstack/ui": "1.7.0",
+    "@checkstack/auth-frontend": "0.6.0",
+    "@checkstack/catalog-common": "2.1.0",
+    "@checkstack/common": "0.9.0",
+    "@checkstack/dashboard-frontend": "0.7.0",
+    "@checkstack/frontend-api": "0.5.0",
+    "@checkstack/incident-common": "1.1.0",
+    "@checkstack/notification-common": "1.0.2",
+    "@checkstack/notification-frontend": "0.4.0",
+    "@checkstack/signal-frontend": "0.1.2",
+    "@checkstack/tips-frontend": "0.2.0",
+    "@checkstack/ui": "1.8.0",
     "date-fns": "^4.1.0",
     "lucide-react": "^0.344.0",
     "react": "^18.2.0",
@@ -31,7 +32,7 @@
   "devDependencies": {
     "typescript": "^5.0.0",
     "@types/react": "^18.2.0",
-    "@checkstack/tsconfig": "0.0.6",
-    "@checkstack/scripts": "0.1.2"
+    "@checkstack/tsconfig": "0.0.7",
+    "@checkstack/scripts": "0.3.1"
   }
 }

package/src/components/IncidentEditor.tsx

@@ -26,6 +26,7 @@ import {
   SelectContent,
   SelectItem,
   StatusUpdateTimeline,
+  LinksEditor,
 } from "@checkstack/ui";
 import { Plus, MessageSquare, Loader2, AlertCircle } from "lucide-react";
 import { IncidentUpdateForm } from "./IncidentUpdateForm";
@@ -86,6 +87,24 @@ export const IncidentEditor: React.FC<Props> = ({
     },
   });
 
+  const addLinkMutation = incidentClient.addLink.useMutation({
+    onSuccess: () => {
+      void refetchDetail();
+    },
+    onError: (error) => {
+      toast.error(extractErrorMessage(error, "Failed to add link"));
+    },
+  });
+
+  const removeLinkMutation = incidentClient.removeLink.useMutation({
+    onSuccess: () => {
+      void refetchDetail();
+    },
+    onError: (error) => {
+      toast.error(extractErrorMessage(error, "Failed to remove link"));
+    },
+  });
+
   // Query for incident details (only when editing)
   const { data: incidentDetail, refetch: refetchDetail } =
     incidentClient.getIncident.useQuery(
@@ -341,6 +360,30 @@ export const IncidentEditor: React.FC<Props> = ({
             </div>
           )}
 
+          {/* Hotlinks (Jira tickets, runbooks, ...) — editing only */}
+          {incident && (
+            <div className="border-t pt-4">
+              <LinksEditor
+                title="Hotlinks"
+                description="Attach Jira tickets, runbooks, dashboards, or any URL relevant to this incident."
+                links={incidentDetail?.links ?? []}
+                busy={
+                  addLinkMutation.isPending || removeLinkMutation.isPending
+                }
+                onAdd={async ({ label, url }) => {
+                  await addLinkMutation.mutateAsync({
+                    incidentId: incident.id,
+                    label,
+                    url,
+                  });
+                }}
+                onRemove={async (link) => {
+                  await removeLinkMutation.mutateAsync({ id: link.id });
+                }}
+              />
+            </div>
+          )}
+
           {/* Team Access Editor - only shown when editing existing incident */}
           {incident?.id && (
             <TeamAccessEditor

package/src/index.tsx

@@ -45,6 +45,7 @@ export default createFrontendPlugin({
     createSlotExtension(UserMenuItemsSlot, {
       id: "incident.user-menu.items",
       component: IncidentMenuItems,
+      metadata: { group: "Reliability" },
     }),
     createSlotExtension(SystemStateBadgesSlot, {
       id: "incident.system-incident-badge",

package/src/pages/IncidentConfigPage.tsx

@@ -11,11 +11,16 @@ import type {
   IncidentWithSystems,
   IncidentStatus,
 } from "@checkstack/incident-common";
-import { incidentAccess } from "@checkstack/incident-common";
+import {
+  incidentAccess,
+  pluginMetadata as incidentPluginMetadata,
+} from "@checkstack/incident-common";
+import { Tip } from "@checkstack/tips-frontend";
 import { CatalogApi } from "@checkstack/catalog-common";
 import {
   Card,
   CardHeader,
+  CardHeaderRow,
   CardTitle,
   CardContent,
   Button,
@@ -210,21 +215,30 @@ const IncidentConfigPageContent: React.FC = () => {
       loading={accessLoading}
       allowed={canManage}
       actions={
-        <Button onClick={handleCreate}>
-          <Plus className="h-4 w-4 mr-2" />
-          Report Incident
-        </Button>
+        <Tip
+          plugin={incidentPluginMetadata}
+          id="report"
+          title="Incidents are deliberate, not automatic"
+          description="Incidents in Checkstack are events you open by hand for real, user-visible problems — they're not auto-created from failing health checks. Use “Report Incident” to record an outage you've detected (your own monitoring, a customer ticket, a security event) so it shows up on the dashboard and the public status page, and so subscribers get notified."
+          side="bottom"
+          align="end"
+        >
+          <Button onClick={handleCreate}>
+            <Plus className="h-4 w-4 mr-2" />
+            Report Incident
+          </Button>
+        </Tip>
       }
     >
       <Card>
         <CardHeader className="border-b border-border">
-          <div className="flex items-center justify-between">
+          <CardHeaderRow>
             <div className="flex items-center gap-2">
               <AlertTriangle className="h-5 w-5 text-muted-foreground" />
               <CardTitle>Incidents</CardTitle>
             </div>
-            <div className="flex items-center gap-4">
-              <label className="flex items-center gap-2 text-sm">
+            <div className="flex flex-wrap items-center gap-3 sm:gap-4">
+              <label className="flex items-center gap-2 text-sm whitespace-nowrap">
                 <input
                   type="checkbox"
                   checked={showResolved}
@@ -239,7 +253,7 @@ const IncidentConfigPageContent: React.FC = () => {
                   setStatusFilter(v as IncidentStatus | "all")
                 }
               >
-                <SelectTrigger className="w-40">
+                <SelectTrigger className="w-full sm:w-40">
                   <SelectValue placeholder="Filter by status" />
                 </SelectTrigger>
                 <SelectContent>
@@ -252,7 +266,7 @@ const IncidentConfigPageContent: React.FC = () => {
                 </SelectContent>
               </Select>
             </div>
-          </div>
+          </CardHeaderRow>
         </CardHeader>
         <CardContent className="p-0">
           {loading ? (
@@ -261,8 +275,22 @@ const IncidentConfigPageContent: React.FC = () => {
             </div>
           ) : incidents.length === 0 ? (
             <EmptyState
+              icon={<AlertTriangle className="size-10" />}
               title="No incidents found"
-              description="No incidents match your current filters."
+              description="Incidents capture real, user-visible problems with the systems you monitor. They're created intentionally — Checkstack does not auto-open them from failed health checks, because not every failed check is a real outage. Open one by hand whenever something's actually broken so it shows up on the dashboard, on the status page, and reaches subscribers."
+              steps={[
+                "Adjust the filters above if you're looking for resolved or older incidents.",
+                "Click “Report Incident” to record an outage you've detected.",
+                "Linked systems and severity drive who gets notified — set them deliberately.",
+              ]}
+              actions={
+                canManage ? (
+                  <Button onClick={handleCreate}>
+                    <Plus className="h-4 w-4 mr-2" />
+                    Report incident manually
+                  </Button>
+                ) : undefined
+              }
             />
           ) : (
             <Table>

package/src/pages/IncidentDetailPage.tsx

@@ -32,6 +32,7 @@ import {
   CheckCircle2,
   Server,
   Plus,
+  ExternalLink,
 } from "lucide-react";
 import { format, formatDistanceToNow } from "date-fns";
 import { IncidentUpdateForm } from "../components/IncidentUpdateForm";
@@ -220,6 +221,28 @@ const IncidentDetailPageContent: React.FC = () => {
                 ))}
               </div>
             </div>
+
+            {incident.links.length > 0 && (
+              <div>
+                <h4 className="text-sm font-medium text-muted-foreground mb-2">
+                  Hotlinks
+                </h4>
+                <div className="flex flex-wrap gap-2">
+                  {incident.links.map((link) => (
+                    <a
+                      key={link.id}
+                      href={link.url}
+                      target="_blank"
+                      rel="noopener noreferrer"
+                      className="inline-flex items-center gap-1 rounded-md border px-2 py-1 text-xs text-primary hover:bg-muted"
+                    >
+                      <ExternalLink className="h-3 w-3" />
+                      <span>{link.label ?? link.url}</span>
+                    </a>
+                  ))}
+                </div>
+              </div>
+            )}
           </CardContent>
         </Card>
 

package/src/pages/SystemIncidentHistoryPage.tsx

@@ -36,7 +36,13 @@ const SystemIncidentHistoryPageContent: React.FC = () => {
   const { data: systemsData, isLoading: systemsLoading } =
     catalogClient.getSystems.useQuery({});
 
-  const incidents = incidentsData?.incidents ?? [];
+  // Sort: active incidents (non-resolved) first, then by creation date desc.
+  const incidents = (incidentsData?.incidents ?? []).toSorted((a, b) => {
+    const aActive = a.status === "resolved" ? 1 : 0;
+    const bActive = b.status === "resolved" ? 1 : 0;
+    if (aActive !== bActive) return aActive - bActive;
+    return new Date(b.createdAt).getTime() - new Date(a.createdAt).getTime();
+  });
   const systems = systemsData?.systems ?? [];
   const system = systems.find((s) => s.id === systemId);
   const loading = incidentsLoading || systemsLoading;
@@ -104,8 +110,8 @@ const SystemIncidentHistoryPageContent: React.FC = () => {
         <CardContent className="p-0">
           {incidents.length === 0 ? (
             <EmptyState
-              title="No incidents"
-              description="This system has no recorded incidents."
+              title="Clean record"
+              description="No incidents have been reported for this system. Incidents in Checkstack are created by hand when a real outage or user-visible issue happens — they aren't auto-generated from failing health checks. Anything reported against this system in the future will show up here."
             />
           ) : (
             <div className="divide-y divide-border">

package/tsconfig.json

@@ -31,6 +31,9 @@
     {
       "path": "../signal-frontend"
     },
+    {
+      "path": "../tips-frontend"
+    },
     {
       "path": "../ui"
     }