Following statement in the Oct. Release was a point of confusion:
“It limits reports that have no route create date in the filter to use a configurable number of days, default to -60 days (down from -90). And it makes the default report's route create date filter configurable, with a default of day -35 (down from day -45).”
But after discussions with Geno, we learned that:
If any report does not have "Create Date (Route)" defined as a filter, the system will default it to -60 days
If a report which has been set as default does not have "Create Date (Route)" defined as a filter, the system will default it to -35 days
In any case if we need to report back beyond these default ranges, we need to specify on our report filters.
Tested by Astro and I in QA we concluded that Oct. release which includes our 2 CMRs are OK to publish to Prod. Since Ace tickets have been removed by MG, we will need to express our confirmation via email
Requested MG to promote to prod:
https://mercurygate.aceproject.com/?TASK_ID=260580
Following statement in the Oct. Release was a point of confusion:
“It limits reports that have no route create date in the filter to use a configurable number of days, default to -60 days (down from -90). And it makes the default report's route create date filter configurable, with a default of day -35 (down from day -45).”
But after discussions with Geno, we learned that:
If any report does not have "Create Date (Route)" defined as a filter, the system will default it to -60 days
If a report which has been set as default does not have "Create Date (Route)" defined as a filter, the system will default it to -35 days
In any case if we need to report back beyond these default ranges, we need to specify on our report filters.
Tested by Astro and I in QA we concluded that Oct. release which includes our 2 CMRs are OK to publish to Prod.
Since Ace tickets have been removed by MG, we will need to express our confirmation via email