Actions
Bug #6013
closedBug #6005: If a node had a date in the future, but returned to current time, the reporting will always be invalid (until it catches up with the future date)
Typo in the migration script for insertionid in reportsexecution
Status:
Released
Priority:
1 (highest)
Assignee:
Category:
Web - Compliance & node report
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
A bad leftover stated in the migration script for the modification of the reportsexecution
Updated by Nicolas CHARLES about 10 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Nicolas CHARLES to Vincent MEMBRÉ
Updated by Nicolas CHARLES about 10 years ago
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset fd48f21cfc3df3d11ce27cf8c660d064a27b7617.
Updated by Jonathan CLARKE about 10 years ago
Applied in changeset f4be2f3345bb13aa083d315b3fd54e38eda119da.
Updated by Vincent MEMBRÉ about 10 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 3.0.0~beta2, which were these days.
- Announcement 3.0
- Changelog 3.0
- Download information: https://www.rudder-project.org/site/get-rudder/downloads/
Actions