Why doesn't the notification tell the user what item they were mentioned in?

When tagging a user in a Document's comment log, their notification tells them they were mentioned but doesn't tell them what document or offer a link in the notification to take them to that document.  

Are we missing a field when creating a document or missing additional information in the comment log when tagging a user?

Parents
  • Hi Jason, I just tested this and it looks like you found a bug! This is specific to the Documents module. If you add a Comment Log entry on a different module, such as Cases, it includes a link to the case in the Related To field on the notification.

    I would recommend submitting a case to Sugar's Support group so they can submit a bug for this; that way, it will be clear that the bug was found externally and is impacting your use of Sugar.

    Good find, and sorry you had to stumble on it!

    -Brenda

  • Hi 

    Was this resolved?


    I am having the same issue, however, this is happening for all modules including Tasks and Cases 

    Enterprise 12.0.3

    Test email received does not include a URL link to the Case or Task

  • Hi , I found the logged issue and it is # 87852. Looks like it is not yet resolved and we haven't received other reports of it. However, as  mentioned, I think your issue is related to the emails received, not the in-app notifications.

    -Brenda

Reply Children
  • Hi 

    Thank you all for the replies Slight smile and raising the log Brenda

    This is the issue I am referring to

    I believe the email that  is referencing is enabled by the 'Email on Mention' setting found in each user's profile:

    Is the issue that you are looking a plain text for the generated email? I believe the record name is hyperlinked if you are viewing the HTML version of the email sent by Sugar.

    I have tested again just to be sure and HTML view and same, there is no hyperlink 

  • Hi , I got a chance to test this in stock 12.0.3 and I see the URL in the email that is sent. It seems like that is not what you are seeing? 

    If not, and if there are no customizations at play here, you may need to file a case with Support to figure out why you are seeing different behavior.

    -Brenda