Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-13776

Duplicate attachments created from images inserted to HTML e-mails when comments added from follow-up messages

    • 23
    • 24
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

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

      Problem Definition

      Each time users that send emails to a designated mailbox from which Jira retrieves them in order to create new tickets or add comments to existing ones usually contain footers with company's logos, marketing imagery or some standard text. All these attachments are autiomatically added to tickets into file attachments therefore cluttering important content.

      Assume the following scenario:
      1. New issue created from an e-mail message (HTML) and image attachment added to the issue
      2. above issue.is commented from the reply e-mail
      Result: the images from original part of message are attached once again.

      With long correspondence the amount of duplicated images becomes VERY big.

      Suggested Solution

      Could we have an option to create filters or a new option in Jira's ticket that allows to remove existing and ignore future content or attachments files in newly retrieved messages? Ideally in files attachments one would click option and select "Remove and ignore" or have a dedicated feature to manageme ignored files and text content that is being removed for each email message going into JIRA. This could be global, per project or even per ticket etc.

            [JRASERVER-13776] Duplicate attachments created from images inserted to HTML e-mails when comments added from follow-up messages

            Sarah A added a comment -

            Hi team, Just a thought, but perhaps AI image recognition capabilities can help to identify repeat images that are not relevant to Jira issues.  

            Sarah A added a comment - Hi team, Just a thought, but perhaps AI image recognition capabilities can help to identify repeat images that are not relevant to Jira issues.  

            MichaelO added a comment -

            @Richard Weilacher, kannst doch nicht erwarten, dass von Atlassian schon nach 16 Jahren ein Bug gefixt wird, geschweige denn ein Vorschlag umgesetzt wird.

            Man ist eher damit beschäftigt, herauszufinden wie man den Kunden noch mehr Kohle aus der Tasche ziehen kann...

            Wir werden in den nächsten Wochen unser Jira abschalten.

             

            MichaelO added a comment - @Richard Weilacher, kannst doch nicht erwarten, dass von Atlassian schon nach 16 Jahren ein Bug gefixt wird, geschweige denn ein Vorschlag umgesetzt wird. Man ist eher damit beschäftigt, herauszufinden wie man den Kunden noch mehr Kohle aus der Tasche ziehen kann... Wir werden in den nächsten Wochen unser Jira abschalten.  

            Why is the categorized as a 'suggestion' and not a defect? Maybe so Atlassian can keep ignoring it?

            Richard Weilacher added a comment - Why is the categorized as a 'suggestion' and not a defect? Maybe so Atlassian can keep ignoring it?

            MichaelO added a comment -

            Yes, thats the really lightning-fast development of Jira....

            MichaelO added a comment - Yes, thats the really lightning-fast development of Jira....

            Bojana Vasic added a comment - - edited

            @John Price
            Thans for your input! Can you please share which JSM version you are on? If I've understood correctly it is working fine for you in JSM but not for JC/JSW (server/dc)?

            I tested in JSM version 4.20.11 (using project based mailchannel) and it works fine, duplicate images from the signatures are not added to issue attachment when comments are comming in. Images from the signatures are added to issue attachment only on create but not after that.
            Though, what I still see as an issue is that signature images are added to the comments...

            Bojana Vasic added a comment - - edited @John Price Thans for your input! Can you please share which JSM version you are on? If I've understood correctly it is working fine for you in JSM but not for JC/JSW (server/dc)? I tested in JSM version 4.20.11 (using project based mailchannel) and it works fine, duplicate images from the signatures are not added to issue attachment when comments are comming in. Images from the signatures are added to issue attachment only on create but not after that. Though, what I still see as an issue is that signature images are added to the comments...

            Still having this issue in Jira Server/DC (not JSM).  I have some issues with 50 copies of email sigs.

            John Price added a comment - Still having this issue in Jira Server/DC (not JSM).  I have some issues with 50 copies of email sigs.

            Please status update on this?

            Thanks!

            Bojana Vasic added a comment - Please status update on this? Thanks!

            This "fix" doesn't work anymore. We still get duplicate attachments after every new comment.

            Javidan Amiraliyev added a comment - This "fix" doesn't work anymore. We still get duplicate attachments after every new comment.

            It great that it was "fixed" in Service Desk 4.8, but not in the newly branded Jira Service Management (server).

            When can we expect a fix in you new flagship offering.

            Based on the length of time this ticket has been opened not holding my breath.

            Created a ticket with with Atlassian, which went no where, except to point me to a third party add on. Third party add on should be for extended functionality not a fix for a core functionality.

            Paul Palasti added a comment - It great that it was "fixed" in Service Desk 4.8, but not in the newly branded Jira Service Management (server). When can we expect a fix in you new flagship offering. Based on the length of time this ticket has been opened not holding my breath. Created a ticket with with Atlassian, which went no where, except to point me to a third party add on. Third party add on should be for extended functionality not a fix for a core functionality.

            Yoav Ashkenazi added a comment - - edited

            If it was fixed in JIRA Service Desk 4.8, it broke really fast, I just tested it on JIRA Service Desk 4.12.2 (https://imgur.com/a/eiTxMG9)

             

            Yoav Ashkenazi added a comment - - edited If it was fixed in JIRA Service Desk 4.8, it broke really fast, I just tested it on JIRA Service Desk 4.12.2 ( https://imgur.com/a/eiTxMG9 )  

              Unassigned Unassigned
              915b63004260 Eugene T.
              Votes:
              249 Vote for this issue
              Watchers:
              131 Start watching this issue

                Created:
                Updated: