-
Type:
Bug
-
Status: Production Complete
-
Priority:
High
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
-
Environment:Production
-
Bug Type:Functional
-
Bug Severity:Low
-
Module:BenAdmin - Report
-
Reported by:Client
-
Company:FDU
-
Item State:Production Complete - Closed
-
Sprint:WT Sprint 31-Bugs
Good day Dev.
Can you please advise why the client received multiple billing reports this morning? Please ref CT-1655 for additional information and screenshot.
Thanks,
Raymond
-
- Time Spent:
- 1h
-
Discussion and code go through on scheduler issue
-
- Time Spent:
- 1h
-
Report Scheduler changes.
-
- Time Spent:
- 1h
-
Discussion on approach to fix the scheduler issue
-
- Time Spent:
- 1h
-
Discussion on approach to fix the scheduler issue
-
- Time Spent:
- 1h
-
Discussion on approach to fix the scheduler issue
-
- Time Spent:
- 5h
-
Code go through to understand implementation
-
- Time Spent:
- 1.5h
-
Discussion with Prasanna Ma'am related to code go through
Created documents for Development and testing Scenarios
-
- Time Spent:
- 0.5h
-
Discussion on scheduler understanding and fix that will be done
-
- Time Spent:
- 4h
-
Service setup on local development machine
Code changes
-
- Time Spent:
- 6.75h
-
Code changes & Debug service
Unit testing
-
- Time Spent:
- 1h
-
Discussion on export scheduler service issue
-
- Time Spent:
- 2h
-
Test scenario go through and discussion
-
- Time Spent:
- 6.5h
-
Discussion on Implementation
Review Testcases
Add new Testcases
Code changes in Impacted Area on Web application
-
- Time Spent:
- 6.25h
-
Changes for Download delivered report popup
Changes for View Calendar
Unit testing
Understand script generation utility to check in DB scripts (DDL, Data Queries)
Discussion With @prasanna ma'am related to exception in Export schedule utility
-
- Time Spent:
- 1h
-
KT-Seesion for ReportTeam
-
- Time Spent:
- 0.5h
-
Code check in in trunk branch
Discussion and Setup export scheduler utility on Prasanna Ma'am Machine
-
- Time Spent:
- 2h
-
Scheduler Setup on local for functionality review
-
- Time Spent:
- 1.5h
-
Code review comments discussion
Code changes based on review comments
-
- Time Spent:
- 2.5h
-
Code review of Scheduler implementation - Changes suggested
-
- Time Spent:
- 5h
-
Code review changes
Unit testing
Check problem to SVN update/Commit/Cleanup, etc
Code check in into trunck branch
-
- Time Spent:
- 2h
-
Discussion an about Add new column to maintain status updated date-time.
Code changes to maintain status updated date-time.
unit testing
Check-in trunk branch
-
- Time Spent:
- 1.5h
-
Code review - Changes suggested related Datetimestamp update
DDL changes for ScheduleStatusID column
-
- Time Spent:
- 2h
-
Code merge into LB branch and check-in in SVN.
-
- Time Spent:
- 2.5h
-
Code Review and functionality Review
-
- Time Spent:
- 3.5h
-
Discussion with QA related to testing scenarios and debug code for reported scenarios
Restore latest soft-choice DB and Verified multiple scenarios on it.
-
- Time Spent:
- 0.75h
-
Report Scheduler -
Scheduler not working
Multiple entries getting set for previous report scheduler issue
One report getting delivered twice
-
- Time Spent:
- 1h
-
Started Testing on LB for all scheduler type.
-
- Time Spent:
- 1h
-
Discussion & changes related to handle schedule pickup functionality
Commit change in Trunk and LB branch
-
- Time Spent:
- 1.5h
-
Analysis and discussion on Report getting scheduled again in case of only once schedule
Code review
-
- Time Spent:
- 3h
-
Merge changes into Ui-Refresh branch
Discussion related to log File size increase on Azure environment
Check code and schedules for companies scheduler is running
-
- Time Spent:
- 0.75h
-
Discussion on Report Logs getting logged on Azure Scheduler - Issue will get resolved with new code checkin
-
- Time Spent:
- 1.5h
-
Code changes merge into stage branch along with parallel report changes
-
- Time Spent:
- 4.5h
-
Discussion about scheduler status with dev team
Stage Testing
-
- Time Spent:
- 0.75h
-
Discussion about scheduler run/status not updated problem with QA & Deployment team
-
- Time Spent:
- 1h
-
Internal discussion about script execution on production (on companies moved from stage to production)
File merge into production branch