-
Bug
-
Resolution: Won't Fix
-
Medium
-
9
-
Severity 2 - Major
-
Summary
Reports showing years are showing the incorrect number of issues when drilling down into the data.
Steps to Reproduce
- Data needs to be collected over many months to see the inconsistencies.
- View a report showing past year by month
- Click on the number for the month to expand the details
Expected Results
The number of issues for the month should for the calendar month. For example, March should return back all the results from March. If 3 issues are shown for March, 3 issues should be displayed.
Actual Results
Issues from February are included in March on the drilled down data, instead of 3 issues being shown 4 are displayed.
Notes
When using month this results in something like:
February 2017 is selected
Period calculated as March 2016 - February 2017
When calculating from this the start and end date for only February it uses the interval duration from first month, which is March.
The problem is that March has more days than February, so it comes up with a period overflowing into March.
The problem is even worse for January, as the code somehow calculated 1 December to 1 30 January as the period, since January has 31 days so it ends up in November before flattening that to the start of the month
Workaround
No workaround.
- duplicates
-
JSDCLOUD-5149 SD reports are showing some issues from March in February drill down
-
- Closed
-
- relates to
-
JSDSERVER-5047 Report Drilldown calculating incorrect period by month
-
- Closed
-
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
- was cloned as
-
SDECO-808 Loading...