fix(app): fix timestamp used for protocol completion #16855
Merged
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
mjhuff
force-pushed
the
app_fix-timestamp-protocol-completion
branch
from
9e53c4b to
e0047a5
Compare
mjhuff
force-pushed
the
app_fix-timestamp-protocol-completion
branch
from
e0047a5 to
9e53c4b
Compare
|
While github takes it's time to process this branch's updates: I thought something odd was going on with the That being said, timestamps aren't continually updated when viewing the |
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.
Closes RQA-3596
Overview
It appears we've been using the
createdAttimestamp instead of thecompletedAttimestamp for last run copy. Whoops.Current Behavior
Screen.Recording.2024-11-15.at.12.24.41.PM.mov
Fixed Behavior
Screen.Recording.2024-11-15.at.1.34.50.PM.mov
Test Plan and Hands on Testing
Changelog
Risk assessment
low