-
Suggestion
-
Resolution: Fixed
-
None
-
121
-
12
-
Problem Definition
Issues created from emails attach files such as marketing advertisment images or even text often included in singatures to an issue, which can clutter things for issue asignees in that they might not be able to filter out important attachments or will lose valuable time in manually deleting attached duplicate files from attachments. Additionally, administrators may want to restrict certain files from a source from being attached to new and existing issues.
Suggested Solution
Implement a file and text filter on a global (JIRA administrators) and/or project (Project administrators) levels to exclude selected attachments or text from email content for new issues as well as comments added to existing.
In orde to manage files exclusions, there would be a select drop-down options next to each attached file allowing to quickly exclude attached files from further inclusions using a combination its name and checksum for uniqueness.
Select drop-down example options:
- 'Exclude' => keeps the original file but prevents further duplicate copies
- 'Remove and exclude' => removes original file and prevents further duplicate copies
A dedicated filters manager would then allow system admins or project managers to manage such exclusions (similar to lists for blocked users in IMs).
Why this is important
Issues with multiple copies of attached files not pertinent to request's problem not only clutter the system but also can cause delays in ticket processing or ticket asignee to miss important attachments in growing list of duplicated files.
- causes
-
JSDSERVER-6884 Some incoming mails containing attachment failed to be processed
-
- Closed
-
- details
-
- Gathering Interest
- is blocked by
-
- Closed
- is related to
-
- Closed
- mentioned in
-
Page Failed to load
-
Page Loading...
-
-
-
-
-
-
-
-
-
- relates to
-
[JSDSERVER-5723] Ignore unwanted images in attachments for issues created from emails
The enterprise track is 4.5 as per https://confluence.atlassian.com/enterprise/atlassian-enterprise-releases-948227420.html
Please put this fix into an enterprise point release.
Hi Rodrigo Baldasso,
It would be a good idea to run at least once in the background (during upgrade etc). or allow admins to do it manually via an admin option a system-wide MD5 re-generation for all existing attachments that don't have MD5 value set on them.
Cheers,
David
Hey a.ayer, Service Desk 4.8.0 is compatible with Jira Software 8.8.0, you can check the compatibility on our compatibility matrix.
ingo.schramme sorry about the release notes containing a broken URL. We'll work to get this sorted!
David's answer is correct.
Basically, duplicate attachments are defined as having the same MD5 hash of the content. File names are not considered. We store hashes in attachment properties' whenever we create them with the feature being turned on. Since existing attachments do not have that data, one occurrence of the clash will still happen - we will create one more attachment with the hash so that no more duplicates are created in the future for the given issue.
Hi Ingo,
It appears from the release notes it's been implemented in the simplest form i.e. JSD will strive to compare attached to email files with those already attached to ticket and ignore any duplicates in the background. My ticket's functionality description would allow more control over attachments and certain exceptions that users might find useful. It was also handling annoying long marketing signatuers that clutter up tickets' content but it's not been mentioned at all hence am assuming as not implemented / ignored. We'll be upgrading our JSD over the next 2-3 weeks and will test what's been implemented in the new release.
Cheers,
David
And how does it work? The Release Notes link directly to this ticket but doesn't mention how it works. Thanks!
The fix is for Service Desk, that's why it is version 4.8.0 and not up in 7.x and 8.x versions, which would apply to Jira Server.
fix for version 4.8.0 What about current releases 7.x and 8.x Jira too?
Totally agreed, that this isn't native functionality is crazy.
Additionally, this would even reduce some of the load on Atlassian's servers, given there would be less files to store / index.
Found a related ticket about fixing this for Cloud: https://jira.atlassian.com/browse/JSDCLOUD-5878