CRM-21446 - Allow case id as well as hash in inbound email processing… #11320
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
… to autofile emails on cases
jitendrapurohit
force-pushed
the
CRM-21446
branch
from
edd1324
to
2019dea
Compare
sluc23
pushed a commit
to ixiam/civicrm-core
that referenced
this pull request
Jan 10, 2018
CRM-21446 - Allow case id as well as hash in inbound email processing…
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.
… to autofill emails on cases
Overview
Allow case id as well as hash in inbound email processing
Before
Only hash is supported for linking activities with cases. See JIRA and https://civicrm.stackexchange.com/questions/21407/how-to-expose-the-civicase-hashed-value-that-gets-sent-in-subject-when-sending-a
After
if the subject contains a text with case id
[case #123]- it will be recorded on the case.Comments
Added unit test to check for hash as well as for case id.
https://issues.civicrm.org/jira/browse/CRM-21446