Closed h-m-f-t closed 1 week ago
@h-m-f-t only one question on this now that I look at it. Do you want these fields showing on the Domain Request page for individual requests or on the Domain Request table shown to analyst in admin?
@abroddrick Good question! I could go either way on this. For now, let's add all the dates to both the individual request page and on the table inside Domain requests
.
Added refinement to make sure the A/C's capture that last 2 comments...
Issue description
We're currently using "submitted date" to mean the last (or latest) time a request entered a submitted state, as there can be submission rounds. Let's add a few fields to domain requests and then update the CSV.
Acceptance criteria
Submitted
(call it first_submitted_date in the code). Note you need to have this be set in the submit() function in domain_requestSubmitted
(this is really a rename of "submission_date" to be called last_submission_date). Check that the migration file says "rename" NOT altered fieldMigrate data
Additional context
if you don't check that the migration says
rename
fromsubmission_date
tolast_submission_date
you will delete every submission date in our database. It NEEDS to sayrename
.Note, for the migration script, you can use audit logs to get the status you need.
Submitted date
], Status, Latest status update...Latest status update
will be the same as theLast submitted date
. That's ok.Talked about in this Slack thread.
Links to other issues