Open Sae126V opened 10 months ago
This PR is ready for review.
When editing a downtime, the start time gets unset. This isn't existing beaviour. Can you track down the cause and fix?
When editing a downtime, the start time gets unset. This isn't existing beaviour. Can you track down the cause and fix?
When editing a downtime, the start time gets unset. This isn't existing beaviour. Can you track down the cause and fix?
This would be fixed by #474 .
@gregcorbett , I have updated the code (some what large parts).
[MAIN Functionality] Added support for selecting multiple sites in "ADD" downtime. Changed the Confirm Downtime and Confirm Edit Downtime pages. Changed Add_Downtime success page with relevant content.
Resolves: https://github.com/GOCDB/gocdb/issues/261
Partially address: https://github.com/GOCDB/gocdb/issues/85 and https://github.com/GOCDB/gocdb/issues/66 .
Addressed @gregcorbett comments:
Suggestion 1:
Include the Site Name next to the downtime link on creation, i.e.:
New Downtimes successfully created. Please click the links below for more information.
Site A: Downtime 10 Site B: Downtime 11
Suggestion 1:
Only display the start and end time once on the "Confirm Downtime" page, i.e.:
Severity: WARNING Description: foo bar Starting (UTC): 08/09/2023 00:00 Ending (UTC): 18/09/2023 00:00 Site Name: Brunnen GS ... Site Name: Torch ...