Edit a CAN

[jonnalley]

User Story

As a budget team member, I need to edit a CAN so that I can provide additional details that didn't come from the system of record.

Preconditions

• A desired CAN record already exists in OPS

Acceptance Criteria

• User (budget team and no others) can provide a total FY budget for the CAN, including carry forward details if applicable for the CAN.
• User can see and validate OPS's calculations for carry-forward details on a multi-year CAN and update as needed.
• User can provide funding received Year to Date
• User can provide CAN nickname and description details
• Users ought not be able to edit other attributes of the CAN (ones that were imported)
• User can choose to revert any changes before proceeding and persistently storing anything
• User can choose to persistently store this data and receive confirmation of the same.

---

Tasks

UX

• Explore design options for creating a CAN (including identifying all the CAN data included)
• Share designs with devs for feedback
• Share designs with OPRE for feedback
• Refine design based on feedback
• Annotate designs and move to Ready for Dev

Dev

FE

• form for CAN details (nickname, description) #3098
• form validation?
• add FY CAN Budget form #3099
• add FY Funding Received form #3100
• Edit CAN Cards #3101
• Funding Received Table #3102
• update Can Budget FY Card to show prev 5 FYs #3232
• display logic for Prev FY Carry Forward Card #3236
• edit button and modal to enter edit-mode #3299
• refactor edit-mode state #3367

BE

• OpenAPI doc: Fix CreateUpdateCANFundingBudgetRequest example #3104
• Remove authorizer and external authorizer attributes #3213
• can_nickname is required field for PATCH to /cans/${id} endpoint #3207
• budget is required field for POST to /can-funding-budgets endpoint #3208
• funding is required field for POST to /can-funding-recieved endpoint #3209
• fix type on can funding summary response #3234
• update logic for carry-forward funds, total - spent, 0 if none #3233

Definition of Done Checklist

• UI works as designed (UX team)
• PR(s) have been merged to main
• Design/tech debt eliminated
• New design/tech debt documented (if applicable)
• Build process updated
• Documentation updated or added
• Feature flags/toggles created

Additional Context & Resources

• Editing the Funding source and Method of Transfer fields will probably come as part of creating a CAN or editing metadata on a CAN
• Anything imported ought not be edited directly by the user, until CANs are re-imported
• Business Rules

[fpigeonjr]

frontend and backend work has started for this story so will remove the tags Dev Frontend Ready and Dev Backend Ready