-
Suggestion
-
Resolution: Unresolved
-
None
-
22
-
15
-
NOTE: This suggestion is for Jira Service Management Data Center. Using Jira Service Desk Cloud? See the corresponding suggestion.
Problem Definition
For Jira Service Management, emails with attachments larger than 25MB will not be pulled by the Jira Service Management Global Puller scheduler job. This is stated in Managing the email channel - Atlassian Documentation.
At the moment, nothing will be thrown in the logs regarding the issue has not been created.
Suggested Solution
Enable the Jira Service Management Global Puller scheduler job to pull emails with attachments larger than 25MB.
- relates to
-
- Gathering Interest
- links to
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSDSERVER-4354] Increase Jira Service Management email attachment size limit
This would make my life much easier. Jira Core itself has this option. Not JSM. Just saying...
When will this feature be available? It is really crucial, especially in the case of forwarded e-mails with larger log-attachments.
Has there already been taken any action concerning this issue? In our company, many e-Mail gets lost, because people are sending us data-loading requests with attachments (=the data to load) > 20MB
From my point of view, there should exist a system-property where the admin can set the max allowed attachment size for der SDS-instance
Please give feedback
Our organisation would also appreciate if we could increase the attachment size for the mail handler, at least to 50 MB.
bryan musgrave
added a comment - I think Jeremy's suggestion would be ideal. Emails should still be processed and it not contain an attachment if attachment was over file size limit. Right now its just a pain that all emails stop being processed once a file is sent over the size limit. We often don't notice this right away too and do a bunch of troubleshooting before finding issue.
bryan musgrave
added a comment - I think Jeremy's suggestion would be ideal. Emails should still be processed and it not contain an attachment if attachment was over file size limit. Right now its just a pain that all emails stop being processed once a file is sent over the size limit. We often don't notice this right away too and do a bunch of troubleshooting before finding issue. 
Jeremy Pieples
added a comment - While allowing user defined max attachment size would be preferable, it would be helpful if the email would at least be processed for a ticket without the attachment. Potentially with a notification on the ticket that there was an attachment but that it was larger than the max attachment size.
Jeremy Pieples
added a comment - While allowing user defined max attachment size would be preferable, it would be helpful if the email would at least be processed for a ticket without the attachment. Potentially with a notification on the ticket that there was an attachment but that it was larger than the max attachment size. 
Beth Wiebusch
added a comment - You allow the issues to have attachments up to 2 gigabyte. Please allow an increase in the attachments that come from email.
Beth Wiebusch
added a comment - You allow the issues to have attachments up to 2 gigabyte. Please allow an increase in the attachments that come from email.
The same issue affects Jira Server and the feature "Get help" in Troubleshooting and Support Tools.
If the logs are too large, error is wthrown while trying to send a help request to Atlassian.
Unable to render embedded object: File (image-2.png?fromIssue=4345717) not found.
What is more, when atlassian.mail.senddisabled=true flag is used while starting Jira (for example on DEV environment for test purposes that needs e-mail features to be disabled) - if you try to use "Get help" feature - there will be a notification that the request was sent, but... it is not. Which is very misleading. This should be fixed as well.
Unable to render embedded object: File (image-2.png?fromIssue=4345717) not found.