-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add start date to report schedule #3701
Conversation
@@ -97,13 +97,13 @@ def get_report_schedule_form_start_date_choice(self): | |||
return self.report_schedule_form_start_date_choice(self.request.POST) | |||
|
|||
def get_report_schedule_form_start_date(self): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this supposed t be on the scheduler view? Its report related right? Maybe this should be on the repor or on a reportView mixin? The same for the following 4 methods.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, I put this in the SchedulerView, but maybe it is better to move it to the BaseReportView. The idea was that the "schedule" is part of the Scheduler as you enter a start date and recurrence which needs form validation from the scheduler side if for example the schedule did not start or Scheduler throws a ConnectionError. The other part is that if we need a scheduler elsewhere where we implement the same start date and recurrence we have it already in place in the SchedulerView.
…ithub.com/minvws/nl-kat-coordination into feature/add-start-date-to-report-schedule
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No remarks
…ithub.com/minvws/nl-kat-coordination into feature/add-start-date-to-report-schedule
That's what you'd expect, right? If you want to schedule it for today, then it should be scheduled for 25-10-2024 00:00, not for the next day (26-10-2024 00:00). Otherwise you should select the 26th. Maybe @HeleenSG has a thought about this: from the user's perspective, what whould you expect to happen? |
@noamblitz the forms with "(Required)" should be fixed now |
…ithub.com/minvws/nl-kat-coordination into feature/add-start-date-to-report-schedule
Created a new ticket to discuss the timestamping issue as mentioned above: #3738. This PR has been tested and it works for now, thus can be merged. |
Quality Gate passedIssues Measures |
* main: Fix reports with organization tags (#3790) Update README.rst - Fix guidelines URLs (#3789) Exclude Report from ooi list (#3768) Update `croniter` (#3767) Fixes for dropdowns (#3732) Fix scheduled Aggregate Report naming (#3748) Make systemctl call for kat-rocky-worker conditional (#3782) Fix vulnerability chapters in Aggregate table of content (#3780) Fix auth token middleware with wrong format header (#3755) Add rocky REST API for report recipes (#3746) Add exception handling to the rest api (#3708) Refactor Multi Report to comply to the new report flow (#3705) Fix report names for scheduled reports (#3726) Fix Multi Report recursion error (#3714) Bump waitress from 3.0.0 to 3.0.1 in /octopoes (#3760) Docs/add muted findings (#3699) Edit report recipe (#3690) Add start date to report schedule (#3701) Add REST API to list report and download pdf report (#3689) Fixes in Report Overview (#3707)
Changes
This PR adds the start date input to the Report Schedule section on the Export Setup page in the report flow.
This allows a user to select the start date of the scheduled report.
It also changes the text “This field is required” to “(Required)” because it was not compliant with the designs. The changes are applied to all forms in KAT.
Issue link
Closes #2779
Demo
QA notes
Code Checklist
.env
changes files if required and changed the.env-dist
accordingly.Checklist for code reviewers:
Copy-paste the checklist from the docs/source/templates folder into your comment.
Checklist for QA:
Copy-paste the checklist from the docs/source/templates folder into your comment.