Skip to content

BDMS-876: Projects view UI#296

Merged
jeremyzilar merged 15 commits into
stagingfrom
BDMS-876-projects-view
Jun 17, 2026
Merged

BDMS-876: Projects view UI#296
jeremyzilar merged 15 commits into
stagingfrom
BDMS-876-projects-view

Conversation

@jeremyzilar

@jeremyzilar jeremyzilar commented Jun 13, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Adds Projects list in the nav and row click to filtered wells view
  • Wells list supports ?projectId= URL filter with indigo filter pill and clear behavior
  • Adds Projects column on wells grid; shared ListPage template and analytics hook
  • Updates primary brand color to indigo across shadcn tokens and MUI theme
  • Contacts create button and wells header actions use shadcn buttons
image image

Test plan

  • Open /ocotillo/well/projects and confirm well counts display
  • Click a project row and confirm wells list filters with project pill
  • Clear project pill and confirm no stale DataGrid filter chip appears
  • Confirm Projects nav stays expanded on wells routes
  • Viewer role can access Projects list (read-only)

Depends on

  • OcotilloAPI PR for well_count and groups filter (point VITE_OCOTILLO_API_URL at API branch or staging after API merge)

Includes project well counts, URL-based project filtering on the wells grid, indigo primary tokens, and filter pill styling.
Brings in the shared Card primitives used by the design system migration.
Moves useState, useEffect, and useOne above early returns so ESLint rules-of-hooks passes.
@github-actions

Copy link
Copy Markdown

Preview Deployment

Preview URL: https://preview-bdms-876-projects-view-auejgdbofq-uc.a.run.app

Note: This preview uses the staging API endpoints.

@jeremyzilar jeremyzilar added the enhancement New feature or request label Jun 13, 2026
@github-actions

Copy link
Copy Markdown

Preview Deployment

Preview URL: https://preview-bdms-876-projects-view-auejgdbofq-uc.a.run.app

Note: This preview uses the staging API endpoints.

1 similar comment
@github-actions

Copy link
Copy Markdown

Preview Deployment

Preview URL: https://preview-bdms-876-projects-view-auejgdbofq-uc.a.run.app

Note: This preview uses the staging API endpoints.

Tracks nav clicks, page templates, project row clicks, filter apply/clear, and project links on the wells grid.
@github-actions

Copy link
Copy Markdown

Preview Deployment

Preview URL: https://preview-bdms-876-projects-view-auejgdbofq-uc.a.run.app

Note: This preview uses the staging API endpoints.

@jirhiker

Copy link
Copy Markdown
Member

Projects are more general than groupings of wells so I don't think the project view should be bound to wells so tightly

@lizalino

Copy link
Copy Markdown

Met with Cris and showed him the Project View table and where the editing capability would exist. He appreciated the view and mentioned a few additional fields he'd like to see, but I want to talk with a few more folks before making these formal requests. I did ask him about the nesting under Wells and he admitted that eventually we would probably want 'Projects' as a top-level, but for now having it under 'Wells' makes sense. In the interest of getting the editing capability underway, I suggest we move on.

…ns to Groups list.

The grid previously showed only name, parent group ID, a boundary checkmark, and created date. Added the remaining fields that the API already returns: description, group_type, release_status (rendered as a chip), well_count, and renamed the project_area column to "Has Boundary" to make the checkmark intent clearer. Also added group_type and well_count to the yup schema so they are not stripped on validation.
@github-actions

Copy link
Copy Markdown

Preview Deployment

Preview URL: https://preview-bdms-876-projects-view-auejgdbofq-uc.a.run.app

Note: This preview uses the staging API endpoints.

1 similar comment
@github-actions

Copy link
Copy Markdown

Preview Deployment

Preview URL: https://preview-bdms-876-projects-view-auejgdbofq-uc.a.run.app

Note: This preview uses the staging API endpoints.

@github-actions

Copy link
Copy Markdown

Preview Deployment

Preview URL: https://preview-bdms-876-projects-view-auejgdbofq-uc.a.run.app

Note: This preview uses the staging API endpoints.

2 similar comments
@github-actions

Copy link
Copy Markdown

Preview Deployment

Preview URL: https://preview-bdms-876-projects-view-auejgdbofq-uc.a.run.app

Note: This preview uses the staging API endpoints.

@github-actions

Copy link
Copy Markdown

Preview Deployment

Preview URL: https://preview-bdms-876-projects-view-auejgdbofq-uc.a.run.app

Note: This preview uses the staging API endpoints.

…dary columns by default.

Projects was nested under Wells in the sidebar. Lifted it to a standalone top-level item so it is directly reachable without expanding Wells first. Also hides the well_count, parent_group_id, and project_area columns by default in the Projects grid — they are still accessible via the Columns toggle.
@github-actions

Copy link
Copy Markdown

Preview Deployment

Preview URL: https://preview-bdms-876-projects-view-auejgdbofq-uc.a.run.app

Note: This preview uses the staging API endpoints.

3 similar comments
@github-actions

Copy link
Copy Markdown

Preview Deployment

Preview URL: https://preview-bdms-876-projects-view-auejgdbofq-uc.a.run.app

Note: This preview uses the staging API endpoints.

@github-actions

Copy link
Copy Markdown

Preview Deployment

Preview URL: https://preview-bdms-876-projects-view-auejgdbofq-uc.a.run.app

Note: This preview uses the staging API endpoints.

@github-actions

Copy link
Copy Markdown

Preview Deployment

Preview URL: https://preview-bdms-876-projects-view-auejgdbofq-uc.a.run.app

Note: This preview uses the staging API endpoints.

@github-actions

Copy link
Copy Markdown

Preview Deployment

Preview URL: https://preview-bdms-876-projects-view-auejgdbofq-uc.a.run.app

Note: This preview uses the staging API endpoints.

@lizalino

Copy link
Copy Markdown

I thought we were removing 'description', otherwise I think this looks good.

@jirhiker

Copy link
Copy Markdown
Member

One option instead of removing description is to use this as an opportunity to test out editing workflow. If we leave description field in we can then signal to the user that editing functionality is on its way

@jeremyzilar jeremyzilar merged commit 305975d into staging Jun 17, 2026
4 of 5 checks passed
@jeremyzilar jeremyzilar deleted the BDMS-876-projects-view branch June 17, 2026 16:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants