cds-snc / cds-snc/platform-forms-client

Investigate what actions change "Date modified" for end user publicly-visible forms [key actions]

Open
#5,775 1 comment 0 reactions 0 assignees View on GitHub
:vertical_traffic_light: Moderate incident
Dominant language
TypeScript
Stars
46
Forks
16
Avg merge
1d 10h
Merged PRs (30d)
82

Description

## Description
As per [#incident-2025-06-20-investigating-validation-issue](https://gcdigital.slack.com/archives/C092D5RD5LL)

**Look into what actions taken on the form impact the “updated_at” value on the publicly visible form**
- We assumed the "date modified" was the "date published" but this was not the case
- Perhaps the "date published" would be a more accurate and useful thing to post
- Should only include updates that affect the public, not just any update

![Image](https://github.com/user-attachments/assets/468f3242-7215-4972-b761-2fc786ab2e2e)

**Related**

#3991
#5545

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the public-facing form behavior described here and the related issues #3991 and #5545, then trace how updated_at and the date published value are exposed. Document which key actions change the publicly visible date, distinguishing public-impacting updates from internal changes; done means the behavior and any recommended date are clearly recorded.

Written by the indexing model from the issue text.

Assessment

Tech stack
nextjs, typescript
Domain
frontend, web-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.