This issue is quite peculiar. I have setup mail handlers and they are working fine except for the below. Attachment size permission permits 1GB files. I have same roles added to permissions for "Create Issue" and "Create Attachment" and "Add comments"
I have added a table which would simplify to know the problem. Please help
1. When a fresh incoming email has <10mb file, new request is created and file is attached. No problem here.
2. When an email is a response to an ongoing email and has <10mb file, comment is added to the existing JIRA request alongwith the attachment. No problem here.
3. When an email is a response to an ongoing email and has >10mb file, comment is added to the existing JIRA request alongwith the attachment. No problem here.
4. When a fresh incoming email has >10mb file, new request is created but file is NOT attached. This is the problem.
Email contain file <10mb | Email contain file >10mb | |
Fresh Email --> creating new request | File is attached in Jira | File is NOT attached in Jira |
Response to an ongoing email --> adding as comments | File is attached in Jira | File is attached in Jira |
Have you tried checking on the email processing logs to see if there is any warning or error?
On top of that, I think it is worth checking the attachment size limit for your mail service as well.
Thank you.
@Victor Law Thank you for responding.
Please help. with the below: I am using JWM and not JSM. I do have "Email request" (which was not under Project settings, i had to use the "Search Jira admin") Under Email Request i do not have anything which says "Processing logs" or any logs for that matter. I used the "Search Jira admin" for 'Logs' and could not find "Processing logs'
The mail service should not be problem because response to an existing ticket with the same attachment gets the attachments added on Jira without any concerns
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Clinton Dsouza I would suggest raising a ticket with a ticket with Atlassian Support, as the team will be able to investigate the behaviour from the logs.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.