hackforla / hackforla/tdm-calculator

Dev: Add Replaced By column to Submissions page table

Open
#3,229 1 comment 0 reactions 0 assignees View on GitHub
deck: staging dependency level: medium p-feature: Manage Submissions p-feature: Submissions and process priority: MUST HAVE role: front-end size: 2pt
Dominant language
JavaScript
Stars
68
Forks
47
Avg merge
3d 9h
Merged PRs (30d)
25

Description

### Dependency
- #3247
At some point, there will be an issue to create a feature that allows an admin to use the Manage Submissions page to set up a Replaced By association as well, but these issues are not yet finalized:
- #2648
- #2876

This dev issue will need to be finalized after the above is resolved.
- #2735

### Overview
We need to add a column called Replaced by to the Submissions page table so that a user can tell which snapshot is connected to a Withdrawn TDM Plan.

### Details

When users look at the Submissions page, they cannot tell which snapshots are connected from Withdrawn TDM Plan → to Submitted TDM Plan. Admins will are able to see the details in the notes on the Manage Submissions page.

To improve visibility:

- Add a new column named Replaced By to the Submissions page table and the Manage Submissions page table
- Add the Replaced By column after the Submission Status column
- For any Withdrawn TDM Plan that has a replacement plan, display the Replacement TDM Plan ID in this column.
- If no replacement exists, leave the field blank.

### Action Items
- [ ] Assign yourself to the development issue.
- [ ] Move the development issue from the Prioritized Backlog to In Progress.
- [ ] Implement the requested change. The project table will have a new column, replacedByProjectId (int) that points to the project that replaces the submitted project. This value can be formatted to get the ten-digit id of the replacement plan. This can use the string type for the column header to get sorting and filtering to work on the new column.
- [ ] Create a PR, if applicable.
- [ ] Create a new slide (or edit one if it already exists) in staging and add the before and after images
- [ ] Once the PR has been approved, use it to close this issue. If there is no PR is associated with this issue, close this issue after lead signoff.

### Resources/Instructions
- Product details: #3181

#### Staging and Release decks
- [Staging Deck](https://docs.google.com/presentation/d/1crZ3IxqA4hAu3qzD7ns93Ieuqjwh6wyEtuX_46cP-fg/)
- [Staging slide, 3229](https://docs.google.com/presentation/d/1crZ3IxqA4hAu3qzD7ns93Ieuqjwh6wyEtuX_46cP-fg/edit?slide=id.g3e352b1d376_31_0#slide=id.g3e352b1d376_31_0)
- Release Deck
- [2026-MM-DD Release deck, slide 3229]

Contributor guide

Open the contributing guide

Research direction

First review dependencies #3247, #2648, #2876, and #2735, since the issue says the work must be finalized after related changes. Then trace the Submissions and Manage Submissions page tables and the project table data described in the issue. Done means both tables show a Replaced By column after Submission Status, display the replacement plan ID for withdrawn plans, and leave it blank when none exists.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
backend, frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.