-
Suggestion
-
Resolution: Unresolved
-
None
-
2
-
2
-
Issue Summary
The JSM mail handler currently only processes emails that are marked as "unread" in a designated custom email address. However, if emails appear as "read" in the inbox, it is not clear whether JSM marked them as "read" or if another factor (such as a mail server rule) did so.
Description
It would be useful that the JSM email puller added a label to emails it processes. This would ensure the admins can tell when an "unread" was marked by something else and the JSM email puller couldn't get to it.
To enhance clarity and management, it would be beneficial for the JSM email puller to add a label to the emails it processes. This labelling would allow administrators to distinguish between emails marked as "read" by JSM and those altered by other factors, ensuring transparency and better troubleshooting when the JSM email puller can't process an email.
Expected Results
When the JSM mail handler processes an email and marks it as "read" in the custom email address inbox, it should also add a specific label to the email. This label will help identify the action taken by JSM.
Suggested Outlook view
Display a custom label or category for emails processed by JSM to make it easy to filter and identify them.
Suggested Gmail view
Utilise Gmail's labelling feature to tag emails processed by JSM, allowing for straightforward sorting and identification.
Actual Results
When the JSM mail handler processes and marks an email as "read" in the custom email address inbox it is unclear if it was read by JSM or another source (i.e. an agent with access to the email address that checks the email by mistake).
Currently, when the JSM mail handler processes an email and marks it as "read" in the custom email address inbox, there is no indication of whether this action was taken by JSM or another source. This ambiguity can occur if an agent with access to the email address inadvertently checks the email, leading to potential confusion and processing issues.