fix(ux): set first response at even without replied status
#1605
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
ssiyad
force-pushed
the
fix/ux/first_responded_on
branch
from
80230a7 to
63333c3
Compare
Codecov ReportAttention:
📢 Thoughts on this report? Let us know!. |
ssiyad
added a commit
to ssiyad/helpdesk
that referenced
this pull request
Oct 23, 2023
…rappe#1605)" This reverts commit 2da9503.
ssiyad
added a commit
that referenced
this pull request
Oct 23, 2023
* patch(ticket): first response from communication This used to be set from `Replied` status. The logic is then changed to fetch first response from communication instead * Revert "fix(ux): set first response at even without `replied` status (#1605)" This reverts commit 2da9503. * fix(ux): set first response on `Replied` * fix: fetch value directly and avoid update where applicable --------- Co-authored-by: Ankush Menat <[email protected]>
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.
No description provided.