feat: overview page #3694

emlimlf · 2025-12-12T09:33:48Z

In this PR

Changed the default page from the all projects to the overview page
Implemented the new overview page and wired it to the backend

Ticket

Note

Introduces a new Overview as the default landing page showing high‑level metrics and integration health, powered by a new /dashboard/metrics backend endpoint and shared UI components.

Frontend (Overview):
- Add new page modules/admin/modules/overview/pages/overview.vue with sections:
  - Summary cards (People, Organizations, Activities, Sub‑projects) using fetchDashboardMetrics.
  - Integration status chips and detailed list with tabs (In progress, Action required, Failed), filters, pagination, and actions.
- Implement store (overview.store.ts), types, and API service (overview.api.service.ts) using TanStack Query.
- Add filters for project group/project/sub‑project and integration platform.
- Persist selected integration tab via localStorage.
Backend (API/Service):
- New endpoint GET /dashboard/metrics (dashboardMetricsGet.ts) with permission check, returning metrics from DashboardService.getMetrics.
- DashboardService.getMetrics uses data‑access layer; logs and error handling.
- Data access layer: add dashboards module with getMetrics (reads snapshots, falls back to mock) and getProjectsCount; export in package.
Navigation/Routes:
- Default route redirects to /overview and update side menu to "Overview"; add route overview in admin.
UI Kit:
- Add reusable LFX components: Dropdown (selector, item, search, separator), Popover, Chip; styles and responsive util.
- Tailwind config: add shadow xs and minor formatting.
Integrations:
- Add actionRequiredMessage mappings across integration configs; GitHub action supports preventAutoOpen.
- Status config adds chipStatus icon/color used in chips.
Dependencies:
- Add @sxzz/popperjs-es and lodash-es; lockfile updates.

^{Written by Cursor Bugbot for commit 0ce34c9. This will update automatically on new commits. Configure here.}

Signed-off-by: Efren Lim <[email protected]>

github-actions · 2025-12-15T11:39:54Z

⚠️ Jira Issue Key Missing

Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability.

Example:

feat: add user authentication (CM-123)
feat: add user authentication (IN-123)

Projects:

CM: Community Data Platform
IN: Insights

Please add a Jira issue key to your PR title.

cursor · 2025-12-15T11:45:05Z

frontend/src/modules/admin/modules/overview/components/fragments/integration-row.vue

+          <component
+            :is="integration.dropdownComponent"
+            v-if="status.key === 'done' && integration.dropdownComponent.dropdownComponent"
+            :integration="integration"


Bug: Dropdown component receives config instead of status data

The dropdownComponent receives :integration="integration" which passes the config object (from lfIntegrations()), but it should receive :integration="integrationStatus" to match both the actionComponent pattern at line 35 in the same file and the existing integration-list-item.vue pattern. The config object lacks runtime data like id, status, etc. that dropdown components likely need to function correctly.

github-actions · 2025-12-16T04:36:23Z

⚠️ Jira Issue Key Missing

Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability.

Example:

feat: add user authentication (CM-123)
feat: add user authentication (IN-123)

Projects:

CM: Community Data Platform
IN: Insights

Please add a Jira issue key to your PR title.

Signed-off-by: Efren Lim <[email protected]>

github-actions · 2025-12-16T04:49:11Z

⚠️ Jira Issue Key Missing

Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability.

Example:

feat: add user authentication (CM-123)
feat: add user authentication (IN-123)

Projects:

CM: Community Data Platform
IN: Insights

Please add a Jira issue key to your PR title.

cursor · 2025-12-16T04:54:59Z

frontend/src/modules/admin/modules/overview/components/sections/integration-details.vue

+} = OVERVIEW_API_SERVICE.fetchGlobalIntegrations(params);
+
+// @ts-expect-error - TanStack Query type inference issue with Vue
+const totalCount = computed(() => data.value?.pages[0].count || 0);


Bug: Missing optional chaining may cause TypeError

The expression data.value?.pages[0].count uses optional chaining on data.value but not on pages[0]. If data.value exists but pages is an empty array, accessing pages[0] returns undefined, and then accessing .count on it throws a TypeError. The expression needs optional chaining: data.value?.pages?.[0]?.count.

Signed-off-by: Efren Lim <[email protected]>

github-actions · 2025-12-16T05:29:14Z

⚠️ Jira Issue Key Missing

Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability.

Example:

feat: add user authentication (CM-123)
feat: add user authentication (IN-123)

Projects:

CM: Community Data Platform
IN: Insights

Please add a Jira issue key to your PR title.

Signed-off-by: Efren Lim <[email protected]>

github-actions · 2025-12-16T05:30:53Z

⚠️ Jira Issue Key Missing

Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability.

Example:

feat: add user authentication (CM-123)
feat: add user authentication (IN-123)

Projects:

CM: Community Data Platform
IN: Insights

Please add a Jira issue key to your PR title.

github-actions · 2025-12-16T05:31:33Z

⚠️ Jira Issue Key Missing

Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability.

Example:

feat: add user authentication (CM-123)
feat: add user authentication (IN-123)

Projects:

CM: Community Data Platform
IN: Insights

Please add a Jira issue key to your PR title.

Signed-off-by: Efren Lim <[email protected]>

frontend/src/modules/admin/modules/overview/components/sections/integration-details.vue

github-actions · 2025-12-16T05:34:04Z

⚠️ Jira Issue Key Missing

Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability.

Example:

feat: add user authentication (CM-123)
feat: add user authentication (IN-123)

Projects:

CM: Community Data Platform
IN: Insights

Please add a Jira issue key to your PR title.

frontend/src/modules/admin/modules/overview/services/overview.api.service.ts

cursor · 2025-12-16T05:36:12Z

frontend/src/modules/admin/modules/overview/components/fragments/project-filter.vue

+  } else {
+    selectedProject.value = null;
+  }
+}, { immediate: true });


Bug: Project filter doesn't reset sub-project selection on change

When the project selection changes, the sub-project selection is not reset. The project-group-filter.vue correctly clears all child selections (selectedProjectId, selectedSubProjectId, selectedProject, selectedSubProject) when the group changes, but project-filter.vue only updates selectedProject and doesn't clear selectedSubProjectId or selectedSubProject. This causes stale sub-project state when switching between projects, potentially leading to incorrect data filtering since the old sub-project's segment ID remains in the store.

Signed-off-by: Efren Lim <[email protected]>

github-actions · 2025-12-16T07:56:59Z

⚠️ Jira Issue Key Missing

Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability.

Example:

feat: add user authentication (CM-123)
feat: add user authentication (IN-123)

Projects:

CM: Community Data Platform
IN: Insights

Please add a Jira issue key to your PR title.

Signed-off-by: Efren Lim <[email protected]>

github-actions · 2025-12-16T08:11:38Z

⚠️ Jira Issue Key Missing

Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability.

Example:

feat: add user authentication (CM-123)
feat: add user authentication (IN-123)

Projects:

CM: Community Data Platform
IN: Insights

Please add a Jira issue key to your PR title.

cursor · 2025-12-16T08:16:59Z

frontend/src/modules/admin/modules/overview/services/overview.api.service.ts

+    return useQuery<IntegrationProgress[]>({
+      queryKey,
+      queryFn,
+      enabled: !!params.value.segments,


Bug: Query enabled check fails to prevent empty array requests

The enabled: !!params.value.segments condition is intended to disable the query when there are no segments, but an empty array [] is truthy in JavaScript (!![] evaluates to true). When the integration data hasn't loaded yet, segments defaults to an empty array, causing the query to fire immediately with empty segments. The condition needs to also check array length to properly disable the query when there are no segments to query.

Signed-off-by: Efren Lim <[email protected]>

github-actions · 2025-12-16T08:24:20Z

⚠️ Jira Issue Key Missing

Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability.

Example:

feat: add user authentication (CM-123)
feat: add user authentication (IN-123)

Projects:

CM: Community Data Platform
IN: Insights

Please add a Jira issue key to your PR title.

Signed-off-by: Efren Lim <[email protected]>

github-actions · 2025-12-16T08:34:28Z

⚠️ Jira Issue Key Missing

Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability.

Example:

feat: add user authentication (CM-123)
feat: add user authentication (IN-123)

Projects:

CM: Community Data Platform
IN: Insights

Please add a Jira issue key to your PR title.

cursor · 2025-12-16T08:38:12Z

services/libs/data-access-layer/src/segments/index.ts

+        COUNT(*) as "projectsTotal",
+        COUNT(CASE WHEN "createdAt" >= NOW() - INTERVAL '30 days' THEN 1 END) as "projectsLast30Days"
+      FROM segments 
+    `


Bug: Query counts deleted segments despite comment stating otherwise

The getProjectsCount function has a comment explicitly stating "Count all segments not deleted" but the SQL query lacks a WHERE "deletedAt" IS NULL clause. This inconsistency means deleted segments are included in the count, inflating metrics. The codebase consistently uses deletedAt IS NULL filters in other queries (activities, categories, repos) to exclude soft-deleted records.

Signed-off-by: Efren Lim <[email protected]>

github-actions · 2025-12-17T02:31:16Z

⚠️ Jira Issue Key Missing

Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability.

Example:

feat: add user authentication (CM-123)
feat: add user authentication (IN-123)

Projects:

CM: Community Data Platform
IN: Insights

Please add a Jira issue key to your PR title.

emlimlf and others added 29 commits December 3, 2025 17:17

chore: initial commit

ccd61b6

Signed-off-by: Efren Lim <[email protected]>

chore: added project filter

0add8b7

Signed-off-by: Efren Lim <[email protected]>

chore: added integration status section

3891f9f

Signed-off-by: Efren Lim <[email protected]>

chore: added integration details with mock data

a4db2b8

Signed-off-by: Efren Lim <[email protected]>

chore: changed integration row display to match integration page

428fde1

Signed-off-by: Efren Lim <[email protected]>

chore: wire integration tab to api

3beb014

Signed-off-by: Efren Lim <[email protected]>

chore: wired integration details list to api

82939a9

Signed-off-by: Efren Lim <[email protected]>

chore: added sub project filter dropdown

287c88a

Signed-off-by: Efren Lim <[email protected]>

fix: hide project card when project is selected

26e94c9

Signed-off-by: Efren Lim <[email protected]>

feat: add metrics api

c155198

fix: lint

404a959

fix: adjust return type from query

5cdf2e7

fix: return just first value

bcd4407

feat: add project metric

d81be1a

fix: lint

fdf2ea0

refactor: using semgnets entity

3bc2bda

fix: remove deleted at

220ea4b

chore: initial commit

dbb706f

Signed-off-by: Efren Lim <[email protected]>

chore: added project filter

dcd5758

Signed-off-by: Efren Lim <[email protected]>

chore: added integration status section

2e54ebb

Signed-off-by: Efren Lim <[email protected]>

chore: added integration details with mock data

4dc78d7

Signed-off-by: Efren Lim <[email protected]>

chore: changed integration row display to match integration page

df239fb

Signed-off-by: Efren Lim <[email protected]>

chore: wire integration tab to api

20a17f6

Signed-off-by: Efren Lim <[email protected]>

chore: wired integration details list to api

4c231e5

Signed-off-by: Efren Lim <[email protected]>

chore: added sub project filter dropdown

c0bce74

Signed-off-by: Efren Lim <[email protected]>

fix: hide project card when project is selected

9f24898

Signed-off-by: Efren Lim <[email protected]>

fix: merge conflict

59c65e3

Signed-off-by: Efren Lim <[email protected]>

chore: wired summary cards to backend

2d68eb0

Signed-off-by: Efren Lim <[email protected]>

fix: previous value computation

cc3dc14

Signed-off-by: Efren Lim <[email protected]>

emlimlf requested a review from gaspergrom December 12, 2025 09:33

fix: dropdown item types

a8f7268

Signed-off-by: Efren Lim <[email protected]>

cursor bot reviewed Dec 15, 2025

View reviewed changes

Merge branch 'main' into feat/overview-page

d4a0c84

emlimlf added 2 commits December 16, 2025 12:44

fix: multiple popups opened

d2ff8b5

Signed-off-by: Efren Lim <[email protected]>

fix: integration filter width and overview page width

92c27cf

Signed-off-by: Efren Lim <[email protected]>

cursor bot reviewed Dec 16, 2025

View reviewed changes

chore: testing progress list api

91a122e

Signed-off-by: Efren Lim <[email protected]>

fix: page width

e106559

Signed-off-by: Efren Lim <[email protected]>

chore: lint issues

60b932b

Signed-off-by: Efren Lim <[email protected]>

cursor bot reviewed Dec 16, 2025

View reviewed changes

frontend/src/modules/admin/modules/overview/components/sections/integration-details.vue Outdated Show resolved Hide resolved

cursor bot reviewed Dec 16, 2025

View reviewed changes

chore: added display for in progress

2501fc5

Signed-off-by: Efren Lim <[email protected]>

fix: github nango display

7a2086b

Signed-off-by: Efren Lim <[email protected]>

cursor bot reviewed Dec 16, 2025

View reviewed changes

fix: inccorect tab key used

22f98f6

Signed-off-by: Efren Lim <[email protected]>

fix: status alignment

743ce91

Signed-off-by: Efren Lim <[email protected]>

cursor bot reviewed Dec 16, 2025

View reviewed changes

feat: added action required messages

0ce34c9

Signed-off-by: Efren Lim <[email protected]>

feat: overview page #3694

Are you sure you want to change the base?

feat: overview page #3694

Conversation

emlimlf commented Dec 12, 2025 • edited by cursor bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

In this PR

Ticket

Uh oh!

github-actions bot commented Dec 15, 2025

Uh oh!

cursor bot Dec 15, 2025

Choose a reason for hiding this comment

Bug: Dropdown component receives config instead of status data

Uh oh!

github-actions bot commented Dec 16, 2025

Uh oh!

github-actions bot commented Dec 16, 2025

Uh oh!

cursor bot Dec 16, 2025

Choose a reason for hiding this comment

Bug: Missing optional chaining may cause TypeError

Uh oh!

github-actions bot commented Dec 16, 2025

Uh oh!

github-actions bot commented Dec 16, 2025

Uh oh!

github-actions bot commented Dec 16, 2025

Uh oh!

Uh oh!

github-actions bot commented Dec 16, 2025

Uh oh!

Uh oh!

cursor bot Dec 16, 2025

Choose a reason for hiding this comment

Bug: Project filter doesn't reset sub-project selection on change

Uh oh!

github-actions bot commented Dec 16, 2025

Uh oh!

github-actions bot commented Dec 16, 2025

Uh oh!

cursor bot Dec 16, 2025

Choose a reason for hiding this comment

Bug: Query enabled check fails to prevent empty array requests

Uh oh!

github-actions bot commented Dec 16, 2025

Uh oh!

github-actions bot commented Dec 16, 2025

Uh oh!

cursor bot Dec 16, 2025

Choose a reason for hiding this comment

Bug: Query counts deleted segments despite comment stating otherwise

Uh oh!

github-actions bot commented Dec 17, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

emlimlf commented Dec 12, 2025 •

edited by cursor bot

Loading