Jira corrupts summary/subject when issue is created from email with Cyrillic characters

XMLWordPrintable

    • 6
    • Severity 3 - Minor
    • Hide
      Atlassian Update – 06 December 2017

      Hi everyone,

      We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to resolve it as Time Out.

      Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Jira team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bugfix Policy for more details.

      We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication.
      Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments.
      Thank you,
      Ignat Alexeyenko
      Jira Bugmaster

      Show
      Atlassian Update – 06 December 2017 Hi everyone, We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to resolve it as Time Out . Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Jira team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bugfix Policy for more details. We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication. Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments. Thank you, Ignat Alexeyenko Jira Bugmaster

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

      When I use the UTF-8 chars all is good when you switch to Cyrillic it breaks.

      When sending an email with the following subject:
      "это тестовый очень длинный заголовок для проверки обрезания"
      this will result in the issue summary:
      "это тестовый очень =?UTF-8?B?0LTQu9C40L3QvdGL0Lkg0LfQsNCz0L7Qu9C+0LLQvtC6INC00LvRjyDQv9GA0L7QstC10YDQutC4INC+?==?UTF-8?B?0LHRgNC10LfQsNC90LjRjw==?="

      In the debug I find logs of the following:

      2013-03-01 14:50:14.827881500 2013-03-01 13:50:14,827 QuartzScheduler_Worker-0 DEBUG ServiceRunner    <mailhandlername> [com.atlassian.mail.incoming] * 2 FETCH (RFC822.SIZE 2999 ENVELOPE ("Fri, 1 Mar 2013 11:48:49 +0100" "=?KOI8-R?B?bWFkYWdhc2NhcnRjLnJ1INzUzyDUxdPUz9fZyiDP3sXO2CA=?==?KOI8-R?B?xMzJzs7ZyiDawcfPzM/Xz8sgxMzRINDSz9fF0svJIM8=?==?KOI8-R?B?wtLF2sHOydE=?=" (("Bastiaan Jansen" NIL "bjansen" "atlassian.com")) (("Bastiaan Jansen" NIL "bjansen" "atlassian.com")) (("Bastiaan Jansen" NIL "bjansen" "atlassian.com")) ((NIL NIL "jira" "<mailserver>")) NIL NIL NIL "<CABQyTP_sgo+VR4Yb6cjZ+1twD3V93HbCJzJtKZWB0cdQiCQ3mw@mail.gmail.com>") INTERNALDATE "01-Mar-2013 10:48:52 +0000")

      Note the 

      =?KOI8-R?B?bWFkYWdhc2NhcnRjLnJ1INzUzyDUxdPUz9fZyiDP3sXO2CA=?==?KOI8-R?B?xMzJzs7ZyiDawcfPzM/Xz8sgxMzRINDSz9fF0svJIM8=?==?KOI8-R?B?wtLF2sHOydE=?=

      That character string should be the summary. KOI8-R is an enconding that is used for Cyrillic characters. It looks like the encoding is opened and midway closed again. This could be the cause for the weird character set in the issue summary.

            Assignee:
            Unassigned
            Reporter:
            Bastiaan Jansen (Inactive)
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: