-
Bug
-
Resolution: Won't Fix
-
Low
-
None
-
5.2.1
-
None
-
5.02
-
This was a known issue where we have a KB article explained the phenomenon of the encoding affects the creation of jira issue and provided resolution for:
Stacktrace in incoming-mail.log:
[Created via e-mail received from: XXXXX XXXXX<XXXX.XXXXX@XXXXX.com>]][priority,3][timeestimate,null][duedate,null][timeoriginalestimate,null][watches,0][key,XXXX-410] (SQL Exception while executing the following:INSERT INTO jiraissue (ID, pkey, PROJECT, REPORTER, ASSIGNEE, issuetype, SUMMARY, DESCRIPTION, ENVIRONMENT, PRIORITY, RESOLUTION, issuestatus, CREATED, UPDATED, DUEDATE, RESOLUTIONDATE, VOTES, WATCHES, TIMEORIGINALESTIMATE, TIMEESTIMATE, TIMESPENT, WORKFLOW_ID, SECURITY, FIXFOR, COMPONENT) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) (Incorrect string value: '\xE2\x80\x91Mai...' for column 'DESCRIPTION' at row 1)) at com.atlassian.jira.workflow.OSWorkflowManager.createIssue(OSWorkflowManager.java:848) at com.atlassian.jira.issue.managers.DefaultIssueManager.createIssue(DefaultIssue[Created via e-mail received from: XXXXXX <XXX.XXX@XXXX.com>]][priority,3][timeestimate,null][duedate,null][timeoriginalestimate,null][watches,0][key,BPW-410] (SQL Exception while executing the following:INSERT INTO jiraissue (ID, pkey, PROJECT, REPORTER, ASSIGNEE, issuetype, SUMMARY, DESCRIPTION, ENVIRONMENT, PRIORITY, RESOLUTION, issuestatus, CREATED, UPDATED, DUEDATE, RESOLUTIONDATE, VOTES, WATCHES, TIMEORIGINALESTIMATE, TIMEESTIMATE, TIMESPENT, WORKFLOW_ID, SECURITY, FIXFOR, COMPONENT) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) (Incorrect string value: '\xE2\x80\x91Mai...' for column 'DESCRIPTION' at row 1)) at com.atlassian.jira.workflow.OSWorkflowManager.createIssue(OSWorkflowManager.java:848) at com.atlassian.jira.issue.managers.DefaultIssueManager.createIssue(DefaultIssueManager.java:440) ... 14 more Caused by: com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericEntityException: while inserting: [GenericEntity:Issue][summary,eToken - XXXXXX XXXXXX XXXXXXXXX ändeXX][status,1][votes,0][assignee,risto][security,null][resolutiondate,null][type,9][timespent,null][id,10773][reporter,risto][project,10001][environment,null][created,2013-01-15 16:40:40.547][updated,2013-01-15 16:40:40.547][workflowId,10773][description,
Consequences:
- If customer has hundreds of emails not accepted by JIRA mail handler and created as issue, the issue count would be suddenly increase by a huge number in one night.
Suggestion:
- If the mail was not accepted and created as issue in JIRA, the pcounter shouldn't be increase at all in the project table.