Done
Details
Assignee
Siarhei HrabkoSiarhei HrabkoReporter
Kruthi VuppalaKruthi VuppalaTester Assignee
Siarhei HrabkoSiarhei HrabkoLabels
Priority
P3Story Points
2Sprint
NoneDevelopment Team
ThunderjetFix versions
TestRail: Cases
Open TestRail: CasesTestRail: Runs
Open TestRail: Runs
Details
Details
Assignee
Siarhei Hrabko
Siarhei HrabkoReporter
Kruthi Vuppala
Kruthi VuppalaTester Assignee
Siarhei Hrabko
Siarhei HrabkoLabels
Priority
Story Points
2
Sprint
None
Development Team
Thunderjet
Fix versions
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created January 2, 2020 at 3:48 PM
Updated April 30, 2020 at 11:33 AM
Resolved April 30, 2020 at 11:33 AM
Overview
This was observed on the start of a new year. For the existing sample data with FY records only for FY18 and FY19, there was no ledgerFY record present. Hence the insertion of transaction records was failing with ledgerFY record not being present.
We need to handle the scenario of making the ledgerFY record available for past years.
Currently we are creating ledgerFY records for FYs where, periodEnd > now
Approach
Upon creation of a fiscal year, check if there any ledgers using that FY series. If so, create a ledgerFY record, regardless of the periodEnd value.
Upon creation of a ledger, create ledgerFY records for each FY in the series, regardless of whether they're in the past, present or future.
Acceptance Criteria
LedgerFY records are always created as needed (upon FY and Ledger creation)
Unit tests are updated