Update oplog_import.html #434
Open
+1
−1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Indicate that timezone offset is required.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Indicate that timezone offset is required.
Identify the Bug
#433
Description of the Change
Change YYYY-MM-DD HH:MM:SS to YYYY-MM-DD HH:MM:SS+00:00.
This is a small change that aims to increase clarity of the required format for start_date and end_date fields when uploading custom Operation Logs. Using the YYYY-MM-DD HH:MM:SS format results in the bug identified above. Using the YYYY-MM-DD HH:MM:SS+00:00 format fixes the bug.
Alternate Designs
Could use a general plus/minus HH:MM indicator of timezone offset.
Possible Drawbacks
N/A
Verification Process
It is a 6 character addition to an existing line in the ghostwriter/oplog/templates/oplog/oplog_import.html file.
Release Notes