Clearly log when a booking gets split in its log #4031
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
It covered its trigger element and immediately disappeared after opening (chrome) or even flickered (firefox), making it basically unreadable.
ThiefMaster
force-pushed
the
split-bookings-log
branch
from
aa7a298
to
a96114d
Compare
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.
Right now we have absolutely nothing in the log of any of the bookings when editing it resulted in a split, which leads to confused users (team members: see
INC2082467) and wasted time for everyone involved when trying to figure out what happened.We should log:
Instead of the booking ID we could also include the link to the other booking... again, probably not clickable, but makes figuring out what happened so much easier...