Year field on acq fund should link to acq fiscal year
Bug #2021996 reported by
Tiffany Little
This bug affects 4 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Sparked by bug 2021992.
The year field on the table acq.fund is purely a text field; you can enter whatever number that you like into it. When creating a fund, it's just a freetext field. As a sidenote, that undoubtedly means that you could do things like create "2022" and also "2022_" (with a space on the end) and that's probably problematic to someone somewhere. But I digress.
The Year field should reference the acq.fiscal_year table, so that you can only make selections from entries in that table.
description: | updated |
Changed in evergreen: | |
status: | New → Confirmed |
To post a comment you must log in.
To clarify, acq.fund.year is an integer field, so "2022_" is not in the cards - and more to the point, nor is the likes of "2023-2024".
Regardless, I agree with the point that acq.fund.year (maybe renamed to acq.fund. fiscal_ year or acq.fund. fiscal_ period) should be a link to acq.fiscal_year. If we do that, I also think that acq.fiscal_ year.year should be changed from an integer field to a text field. We should also give some consideration to adding an org owner column to acq.fiscal_year, as there's no guarantee that all members of a consortium would have the same fiscal period.