Uploaded image for project: 'Xporter for Jira Cloud'
  1. Xporter for Jira Cloud
  2. XPORTERCLOUD-2566

As a User, I should be able to send scheduled reports with the corporate email address displayed as the sender

    XporterXMLWordPrintable

Details

    • Suggestion
    • Status: Closed
    • Resolution: Unresolved
    • None
    • None
    • None
    • None
    • UI

    • UNCOVERED

    Description

      Description

      When users send scheduled reports, the sender email currently does not reflect the corporate email address. Users should be able to configure scheduled reports to be sent from the official corporate email, ensuring consistency, professionalism, and trust for recipients.

      User friction

      Recipients may not recognize or trust emails sent from non-corporate or system-generated addresses. This can lead to confusion, reduced credibility, or emails being ignored or flagged as spam. Internally, users lack control over branding and communication standards.

      Steps to reproduce (right now) / Actual Result:

      • Schedule a report for automatic sending.
      • Configure recipients and timing.
      • Send or wait for the scheduled report to be delivered.

      Actual Result:
      The email is sent from a default/system-generated sender address instead of the corporate email

      IMPACT

      What would improve if solved:

      • Consistent corporate branding in communications
      • Increased trust and open rates from recipients
      • Reduced confusion about email origin
      • Better alignment with company communication policies

      Impact on stakeholders:

      • Gain control over sender identity and improve communication quality
      • More likely to trust and engage with reports
      • Maintains brand consistency and professionalism

      Current workaround:

      Users can manually download reports and resend them using their corporate email address.

      CONTEXT & EXAMPLES:

      Concrete example:

      A user schedules a weekly performance report to be sent to clients. The email arrives from a generic system address rather than the company’s official email, prompting clients to question its authenticity.

      Workaround risk:

      • Manual effort increases the risk of delays or missed reports
      • Higher chance of human error (wrong attachment, outdated data)
      • Inefficient and not scalable for frequent reporting
      • Inconsistent delivery experience for recipients

      Attachments

        Issue Links

          Activity

            People

              crmc Cristiano Cunha
              ana.ribeiro Ana Ribeiro
              Votes:
              1 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated: