[Bug 1479858] [NEW] Relative periods (Reporting Month, month this year) in Standard Reports returns wrong periods

Support - Assistance technique
1

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

2

** Changed in: dhis2
       Status: New => In Progress

** Changed in: dhis2
     Assignee: (unassigned) => John Francis Mukulu (john-f-mukulu)

···

--
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:
  In Progress

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

3

Bug introduced on release of This relative period on version 2.19,
Standard report parameters where saved to last relative period causing
choices to be dated back by one period.

On release of 2.21 Change of Report enum type "html" to "HTML" caused html report to be redirected pdf generation.
Both issues fixed.

** Changed in: dhis2
       Status: In Progress => Fix Committed

···

--
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:
  Fix Committed

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

4

Dear John,

Thanks for fixing this.
Is it backported to 2.20 too?

Alex

···

On Tue, Oct 27, 2015 at 11:57 AM, John Francis Mukulu < 1479858@bugs.launchpad.net> wrote:

Bug introduced on release of This relative period on version 2.19,
Standard report parameters where saved to last relative period causing
choices to be dated back by one period.

On release of 2.21 Change of Report enum type "html" to "HTML" caused html
report to be redirected pdf generation.
Both issues fixed.

** Changed in: dhis2
       Status: In Progress => Fix Committed

--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1479858

Title:
  Relative periods (Reporting Month, month this year) in Standard
  Reports returns wrong periods

Status in DHIS:
  Fix Committed

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

--
Alex Tumwesigye

Technical Advisor - DHIS2 (Consultant),
Ministry of Health/AFENET
Kampala
Uganda

IT Consultant - BarefootPower Uganda Ltd, SmartSolar, Kenya

IT Specialist (Servers, Networks and Security, Health Information Systems -
DHIS2 ) & Solar Consultant

+256 774149 775, + 256 759 800161

"I don't want to be anything other than what I have been - one tree hill
"

--
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:
  Fix Committed

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

5

Yes Alex, It is.

Most recent build is on Jenkins CI server:
https://apps.dhis2.org/ci/job/dhis-2.20/

You can find details of changes here:
https://apps.dhis2.org/ci/job/dhis-2.20/changes

···

--
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:
  Fix Committed

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

6

Hello from the the future!

This issue is in v2.39.3 :slight_smile:

7

Hi Chase,

Do you know if there’s an existing Jira issue for this? Thanks!