Issue Keys Not Created Sequentially
プラットフォームについて: Data Center - この記事は、Data Center プラットフォームのアトラシアン製品に適用されます。
このナレッジベース記事は製品の Data Center バージョン用に作成されています。Data Center 固有ではない機能の Data Center ナレッジベースは、製品のサーバー バージョンでも動作する可能性はありますが、テストは行われていません。サーバー*製品のサポートは 2024 年 2 月 15 日に終了しました。サーバー製品を利用している場合は、アトラシアンのサーバー製品のサポート終了のお知らせページにて移行オプションをご確認ください。
*Fisheye および Crucible は除く
問題
Issue key is not following in sequence when creating issue in JIRA.
atlassian-jira-incoming-mail.log: に次のメッセージが出力される。
2015-10-27 09:49:03,162 WARN [XXXXX] QuartzScheduler_Worker-1 ServiceRunner XXX XXX[10000]: Unable to create issue with message.
com.atlassian.jira.exception.CreateException: com.atlassian.jira.workflow.WorkflowException: org.ofbiz.core.entity.GenericEntityException: while inserting: [GenericEntity:Issue][summary,XXX][status,10017][votes,0][assignee,XXX][number,11316][security,null][resolutiondate,null][type,8][timespent,null][creator,null][id,71514][reporter,XXX][project,10500][environment,null][created,2015-10-27 09:49:03.132][updated,2015-10-27 09:49:03.132][workflowId,79526][priority,5][description,
...
][timeestimate,null][duedate,null][timeoriginalestimate,null][watches,0]
(SQL Exception while executing the following:INSERT INTO jiraissue (ID, pkey, issuenum, PROJECT, REPORTER, ASSIGNEE, CREATOR, 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\x8BSta...' for column 'DESCRIPTION' at row 1))
at org.ofbiz.core.entity.GenericDAO.singleInsert(GenericDAO.java:200)
at org.ofbiz.core.entity.GenericDAO.insert(GenericDAO.java:165)
at org.ofbiz.core.entity.GenericHelperDAO.create(GenericHelperDAO.java:83)
at org.ofbiz.core.entity.GenericDelegator.create(GenericDelegator.java:526)
at org.ofbiz.core.entity.GenericDelegator.create(GenericDelegator.java:513)
at org.ofbiz.core.entity.GenericValue.create(GenericValue.java:98)
at com.atlassian.jira.ofbiz.DefaultOfBizDelegator.createValue(DefaultOfBizDelegator.java:390)
... 22 more診断
次の SQL を実行します。
- The highest issue key is:
select MAX(j.issuenum) from project p,jiraissue j where p.id=j.project and p.pname='<project name>';
Replace <project name> with the respective exact project name.
- This will tell us where the counter is, so that when the next issue is created the counter will be incremented by 1 and assigned to the issue key:
select pcounter from project where pname='<project name>'; Replace <project name> with the respective exact project name.
If the SQL returns different values, then this is relevant. If the same value is being returned, then please get in touch with Atlassian Support with a fresh new Support ZIP.
MySQL note
If you are running MySQL, the counters might match, and this KB will apply anyway.
Check for the "Incorrect string value" error followed by a string value, then check the MySQL database collation and character set. MySQL running on utf8_bin encoding will not recognize emojis properly.
If you would like to verify the message, you can match up the string value that is listed to a the unicode for an emoji here: https://unicode.org/emoji/charts/full-emoji-list.html
原因
The issue creation from email is failing due to mismatch database collation.
ソリューション
Please fix the database collation as per: