dhis2-devs team mailing list archive
-
dhis2-devs team
-
Mailing list archive
-
Message #38775
[Bug 1479858] [NEW] Relative periods (Reporting Month, month this year) in Standard Reports returns wrong periods
Public bug reported:
Relative periods (Reporting Month, month this year) in Standard Reports
returns wrong periods.
For example:
When you edit a standard report, tick reporting month and save. When you run the report, it returns the chosen period minus one e.g July 2015 will return data of June 2015 (201506 as a period when using the web browser console).
Also the relative period save on return to edit the report is unchecked.
Checking analytics, everything works as expected.
I went ahead check the database for relative periods table "relativeperiods", many new relativeperiodsids are generated instead of using the existing ones and are set null instead of either true or false.
This affects version 2.19, tested on dhis2 demo, on my own
test/production server build revision 19266 and several build revisions
below.
The reports tested with a HTML reports.
** Affects: dhis2
Importance: Undecided
Status: New
** Tags: 2.19
** Attachment added: "This is a screenshot showing the error"
https://bugs.launchpad.net/bugs/1479858/+attachment/4436277/+files/Relative%20period%20bug.png
--
You received this bug notification because you are a member of DHIS 2
developers, which is subscribed to DHIS.
https://bugs.launchpad.net/bugs/1479858
Title:
Relative periods (Reporting Month, month this year) in Standard
Reports returns wrong periods
Status in DHIS:
New
Bug description:
Relative periods (Reporting Month, month this year) in Standard
Reports returns wrong periods.
For example:
When you edit a standard report, tick reporting month and save. When you run the report, it returns the chosen period minus one e.g July 2015 will return data of June 2015 (201506 as a period when using the web browser console).
Also the relative period save on return to edit the report is unchecked.
Checking analytics, everything works as expected.
I went ahead check the database for relative periods table "relativeperiods", many new relativeperiodsids are generated instead of using the existing ones and are set null instead of either true or false.
This affects version 2.19, tested on dhis2 demo, on my own
test/production server build revision 19266 and several build
revisions below.
The reports tested with a HTML reports.
To manage notifications about this bug go to:
https://bugs.launchpad.net/dhis2/+bug/1479858/+subscriptions
Follow ups