fix: incorrect followup urls #5863
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
The mark_as_read action was not redirecting to the case contact that it was marking as read.
elasticspoon
force-pushed
the
fix/incorrect-followup-urls
branch
from
5d929ed
to
13d5e45
Compare
elasticspoon
requested review from
compwron,
FireLemons and
littleforest
as code owners
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.
The mark_as_read action was not redirecting to the case contact that it was marking as read.
Since we have this mark as read controller action it no longer makes sense to mark a followup to a case contact as read when editing the case contact.