hackforla / hackforla/tdm-calculator
Design: Manage Submissions Modal change to apply withdrawn funds
- Dominant language
- JavaScript
- Stars
- 68
- Forks
- 47
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 25
Description
### Overview
We need to add a field to the Manage Submissions modal, so that withdrawn project funds can be applied to another project ID.
#### Details
**Background**
Sometimes users will need to make a change to a TDM plan after it is submitted, and at the discretion of LADOT they might be able to use the funds from the original paid invoice for the replacement submission.
**Requirements**
The field will have space for a project ID.
- The project can be a draft or a submitted snapshot
- The project can be owned by another user
- The field should be a text entry field, not a drop down.
- The field should show up only if the Admin marks it as "Withdrawn" in the Submission Status field
- I don't know what to call the field; it needs to communicate something to the effect of “Apply withdrawn plan funds to replacement submission"
We had a prior design issue where we were adding the ability to apply withdrawn funds, but it was going to happen on the receiving project. We now want to redesign the process so it happens on the withdrawn project and are expanding it to allow IDs from other users.
- https://github.com/hackforla/tdm-calculator/issues/2648
### Action Items
- [ ] Assign yourself to this issue.
- [ ] Move the issue from Prioritized Backlog to In Progress.
- [ ] In Figma, move a blank page to the Design section.
- [ ] Change the Figma page's title to have the format "#Issue Number | Title | Assignee Name".
- [ ] Copy contents from the Figma Template page to this issue's Figma page.
- [ ] Include a link to this issue's Figma page in the Figma section below.
- [ ] Use the Figma page to design solutions for this issue.
- Once this issue is ready to be reviewed:
- [ ] Add a comment tagging the team design lead that [explains the design](https://github.com/hackforla/tdm-calculator/wiki/Design:-Presentations).
- [ ] Move it to the Visual Review column.
- [ ] Add the "ready for Design lead" label.
- [ ] Once you have received feedback from the design lead, implement feedback as necessary.
- [ ] Use [presentation structure](https://github.com/hackforla/tdm-calculator/wiki/Design:-Presentations) to review proposed designs with the design director. Implement feedback as necessary.
- [ ] Use [presentation structure](https://github.com/hackforla/tdm-calculator/wiki/Design:-Presentations) to review proposed designs with the product, development, and research teams. Implement feedback as necessary.
- [ ] Create a new slide (or edit one if it already exists) in staging and add images and appropriate text
- [ ] Receive design approval from stakeholders. Implement feedback as necessary.
- [ ] Add any annotations to the Figma design that would help the developer with implementation.
- [ ] Create a Ready for Dev section around the final designs on the Figma page.
- [ ] Update the [Figma Design System](https://www.figma.com/design/nD9QK56Mzq7xNSaSUoeGx0/TDM-Calculator?node-id=4041-12655&t=54f7L4Eubz7ppygs-1) with changes resulting from the issue's final design, if applicable.
- [ ] Update the [Style Guide Presentation](https://docs.google.com/presentation/d/1I4q35NL2WW2RpksIyawhHCd8qJnrjme1ZDNIBxu24hQ/), if applicable.
- [ ] Add a comment to the issue that references the final design and adds any annotations that would help the developer with implementation.
- [ ] update https://github.com/hackforla/tdm-calculator/issues/2735 when this issue is done with a link to the final design comment from this issue.
- [ ] Move the Figma page to the Development section of the Figma file.
- [ ] Add the development issue's number in parentheses at the beginning of the title of the Figma page.
- [ ] Include the development handoff issue number in the GitHub section below.
- [ ] Reassign any previous assignees to this issue.
- [ ] Close this issue.
### Resources
#### GitHub
-
#### Figma
-
#### Dev Site
-
#### Staging and Release decks
- [Staging Deck](https://docs.google.com/presentation/d/1crZ3IxqA4hAu3qzD7ns93Ieuqjwh6wyEtuX_46cP-fg/)
- [Staging slide, 2876](https://docs.google.com/presentation/d/1crZ3IxqA4hAu3qzD7ns93Ieuqjwh6wyEtuX_46cP-fg/edit?slide=id.g3c5e3720d55_1_39#slide=id.g3c5e3720d55_1_39)
- Release Deck
- [2026-09-01 Release deck, slide 2876](https://docs.google.com/presentation/d/1uQpewpS226aQFV7ekeZkRzRAcXgvrjvMAE5iRQJt9Zw/edit?slide=id.g3fae594630c_0_0#slide=id.g3fae594630c_0_0)
Contributor guide
Research direction
Start with the requirements in this issue, the prior design issue #2648, and the Design: Presentations guidance. Create the issue’s Figma page from the Figma Template, explore the withdrawn-funds field and modal states, and review the design with the listed stakeholders. Done means an approved, annotated final design is linked here, related issue #2735 is updated, and the handoff materials are complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- figma
- Domain
- design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100