[LS-1005] update date issue in site pop report Created: 13/Mar/26 Updated: 09/Apr/26 Due: 08/Mar/26 Resolved: 09/Apr/26 |
|
| Status: | Closed |
| Project: | L3 Support |
| Component/s: | NEP |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Normal |
| Reporter: | Priyasha Tiwari | Assignee: | Priyasha Tiwari |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | NEP_D | ||
| Remaining Estimate: | 0 minutes | ||
| Time Spent: | 2 days, 4 hours, 30 minutes | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Customer: |
Airtel India
|
| Planned Start: | |
| Planned End: | |
| Defect Category: | Regression |
| Actual Start: | |
| Date of Baselining: |
| Description |
|
SITE POP REPORT CHANGE DATE SHOULD BE SHOWING AS UPDATED DATE IN HEADER .. ALSO SIT EPOP UPDATE DATE IS NOT SHOWING AS SAME AS ROUTE REPORT UPDATE DATE |
| Comments |
| Comment by Srishti Kashyap [ 20/Mar/26 ] |
|
changed header in reports, update date mismatch needs to checked on hold |
| Comment by Srishti Kashyap [ 25/Mar/26 ] |
|
Released build 3.7.71.570 for header change |
| Comment by Srishti Kashyap [ 01/Apr/26 ] |
|
Released Build 3.7.71.576 containing fixes for mismatching in update date. Multiple nodes were being processed for each route, and during each iteration the existing date value in the map was getting replaced. As a result, the final date stored depended on the last processed node, which led to incorrect data. To fix this, instead of directly replacing the values, the logic was updated to retain the earliest insert date and the latest update date, |
| Comment by Priyasha Tiwari [ 09/Apr/26 ] |
|
OK |