search

UserOfficeProject / issue-tracker

Shared place for features and bugs from all collaborators.
0 stars 0 forks source link

Change the create date for imported legacy proposals to their actual create date rather than import date #946

Open georgeflecknell opened 8 months ago

georgeflecknell commented 8 months ago

What is the problem and why is it a problem

This issue affects all users of postgres database data, anyone writing reports with this data and anyone working on the data in the database.

Currently the create date 26-08-22 applies to ALL imported proposals. This is legacy data pulled from the Oracle database on this date. This is not only incorrect, but also prevents reporting using the postgres server alone as a single source of truth.

Affects, reporting tool reports, future report development, custom data exports at User Office request.

Issue not requested but generated as part of continuous improvements. Suggested solution is to copy the SUBMITTED_DATE from legacy data for all affected proposals.

simonfernandes commented 1 month ago

Backlog pruning notes:

Probably more of a developer issue that affects writing custom queries. There are ways around this (querying Allocations instead) but it would still be nice to fix this to avoid confusion in future.