Uploaded image for project: 'Statuspage'
  1. Statuspage
  2. STATUS-960

Email notifications truncate long component names, even though the component management page does not show or enforce a maximum length limit

XMLWordPrintable

    • 2
    • Severity 3 - Minor

      Issue Summary

      Email notifications truncate long component names, even though the component management page does not show or enforce a maximum length limit

      Steps to Reproduce

      • Create a component with a long name;.
      • Trigger a scheduled maintenance or incident that includes this component, prompting an email notification to subscribers.

      Expected Results

      The email notification displays the full component name without truncation.

      Actual Results

      The component name is truncated in the email notification.

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available.

        1. image-2025-03-04-13-25-34-764.png
          image-2025-03-04-13-25-34-764.png
          578 kB

            [STATUS-960] Email notifications truncate long component names, even though the component management page does not show or enforce a maximum length limit

            jhaloot made changes -
            Workflow Original: JAC Bug Workflow v3 [ 4511348 ] New: JAC Bug Workflow v4 [ 4565857 ]
            SET Analytics Bot made changes -
            Support reference count Original: 1 New: 2

            Deeksha added a comment -

            Hi All, 

            This is Deeksha from the product management team. We understand that this can be an issue for some customers, however currently the email template implemented works to provide core information aspects with all details in the link to the incident. 

            We will monitor this ticket in the future to ensure we are updating the email template that solves for all use cases. 

             

            Thank you for providing us your valuable feedback!

            Deeksha added a comment - Hi All,  This is Deeksha from the product management team. We understand that this can be an issue for some customers, however currently the email template implemented works to provide core information aspects with all details in the link to the incident.  We will monitor this ticket in the future to ensure we are updating the email template that solves for all use cases.    Thank you for providing us your valuable feedback!
            Pradip Acharjee made changes -
            Status Original: Needs Triage [ 10030 ] New: Gathering Impact [ 12072 ]
            SET Analytics Bot made changes -
            Support reference count New: 1
            Egor created issue -

              Unassigned Unassigned
              eguzun@atlassian.com Egor
              Affected customers:
              0 This affects my team
              Watchers:
              3 Start watching this issue

                Created:
                Updated: