Uploaded image for project: 'Jira Service Management Cloud'
  1. Jira Service Management Cloud
  2. JSDCLOUD-4354

Increase Jira Service Management email size limit and show failed emails(due to size) in email logs

    • 163
    • 12
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      NOTE: This suggestion is for JIRA Service Desk Cloud. Using JIRA Service Desk Server? See the corresponding suggestion.

      Problem Definition

      As stated in this document, emails with a total size of more than 25MB (including attachments) are not fetched.

      At the moment nothing will be thrown in the logs regarding the mail that has not been created.

      Suggested solution

      • Enable the Jira Service Management email puller to pull emails larger than 25MB.
      • Alert the admin/reporter that their message has not been processed due to email size.
      • Show the failed emails(due to size) under the email logs

            [JSDCLOUD-4354] Increase Jira Service Management email size limit and show failed emails(due to size) in email logs

            Shane Khublall added a comment -

            I'm here as this is now affecting our customers, who have logged tickets with us, but they have been dropped, due to JSM not processing them, and not even showing that there was an error along the way.

             

            This appears to have been created in 2016 -  8 years ago so I'm not very optimistic on a release for this soon.

            Will need to evaluate other service management options to ensure we can deliver consistent support.

            Shane Khublall added a comment - I'm here as this is now affecting our customers, who have logged tickets with us, but they have been dropped, due to JSM not processing them, and not even showing that there was an error along the way.   This appears to have been created in 2016 -  8 years ago so I'm not very optimistic on a release for this soon. Will need to evaluate other service management options to ensure we can deliver consistent support.

            This is a bad behaviour, since neither reporter nor agent know that attachment(s) are  missing, and both of them can miss an important info, it can lead to misunderstandings, confusion and unsatisfied customers and agents.

            Nena Kruljac added a comment - This is a bad behaviour, since neither reporter nor agent know that attachment(s) are  missing, and both of them can miss an important info, it can lead to misunderstandings, confusion and unsatisfied customers and agents.

            Dali added a comment -

            Servus 1bbfd485bf63 

            Is there a rough timeline for when this feature will be released? Because, if it takes a little longer, we would have to switch to another email address and a regular email inbox if necessary, as we receive orders via the JSM.

            Thank you for your effort

            Cheers

            Dali

            Dali added a comment - Servus 1bbfd485bf63   Is there a rough timeline for when this feature will be released? Because, if it takes a little longer, we would have to switch to another email address and a regular email inbox if necessary, as we receive orders via the JSM. Thank you for your effort Cheers Dali

            Dali added a comment -

            Hello there,

            I’m currently also experiencing issues with emails not being delivered due to file size, even though they were slightly under 20MB. However, when I send the same emails from Gmail to Gmail, it works, as the 25MB file size limit in Gmail was sufficient. 

            A log notification for the admins, as well as an automated email to the sender explaining that the email couldn’t be delivered for "this and that reason," would save a lot of pain and prevent many tickets.

            Thx

            Cheers

            Dali added a comment - Hello there, I’m currently also experiencing issues with emails not being delivered due to file size, even though they were slightly under 20MB. However, when I send the same emails from Gmail to Gmail, it works, as the 25MB file size limit in Gmail was sufficient.  A log notification for the admins, as well as an automated email to the sender explaining that the email couldn’t be delivered for "this and that reason," would save a lot of pain and prevent many tickets. Thx Cheers

            Yes a auto reply would solve 80% of the pain.

            Marcel Neyka added a comment - Yes a auto reply would solve 80% of the pain.

            Need to notify the user at least

            Abbie Wells added a comment - Need to notify the user at least

            Penelope van der Lith added a comment - - edited

            This is still a problem, and emails that are well below 25MB are rejected.  I had an email reject that was around 20MB rejected yesterday and again this morning.  

            There is no record of this in the logs, and the reporter did not receive a "bounce" back.

            Penelope van der Lith added a comment - - edited This is still a problem, and emails that are well below 25MB are rejected.  I had an email reject that was around 20MB rejected yesterday and again this morning.   There is no record of this in the logs, and the reporter did not receive a "bounce" back.

            Aj Trellopoulos added a comment - - edited

            I have seen multiple examples of attachments smaller than 25MB not being processed (20-23MB attachments, where the whole email was still under 25MB). The 25MB limit is not correct here.

            Also, the fact that these are blocked silently for the agent side is a problem. Something should alert the agents so they know to check the mailbox.

            Aj Trellopoulos added a comment - - edited I have seen multiple examples of attachments smaller than 25MB not being processed (20-23MB attachments, where the whole email was still under 25MB). The 25MB limit is not correct here. Also, the fact that these are blocked silently for the agent side is a problem. Something should alert the agents so they know to check the mailbox.

            Even if it's not viable to allow large attachments to be uploaded via email, rejecting them silently is a major problem: we miss that customer contact, without realising it, and customer feel ignored. 

            Processing the email without the attachment or at least leaving a message or notification in JSM would allow us to work around this restriction. 

            Henri Seymour {Easy Agile} added a comment - Even if it's not viable to allow large attachments to be uploaded via email, rejecting them  silently is a major problem: we miss that customer contact, without realising it, and customer feel ignored.  Processing the email without the attachment or at least leaving a message or notification in JSM would allow us to work around this restriction. 

            Large emails will slow down the service, and probably provide a security risk. And I guess they take up space on Atlassian's servers.

            Bearing that in mind:

            50mb is fine, but please please please create the ticket with a note saying: "Attachments not supplied due to file size limitations."

            Or something similar.

            Please.

            Ollie Reynolds added a comment - Large emails will slow down the service, and probably provide a security risk. And I guess they take up space on Atlassian's servers. Bearing that in mind: 50mb is fine, but please please please create the ticket with a note saying: "Attachments not supplied due to file size limitations." Or something similar. Please.

              1bbfd485bf63 Ben Costello
              rvasudiven Ranjen Vasudiven (Inactive)
              Votes:
              143 Vote for this issue
              Watchers:
              135 Start watching this issue

                Created:
                Updated: