[JIRA] (JENKINS-57814) The unicode of Jira changelog maybe incorrect

Issue Type:	Bug
Assignee:	Wisen Tanasa
Attachments:	image-2019-06-03-14-48-39-650.png, image-2019-06-03-15-10-35-058.png, image-2019-06-03-15-14-52-729.png
Components:	jira-trigger-plugin
Created:	2019-06-03 07:21
Environment:	Jira Server 6.4.5 + Jenkins Jira Trigger Plugin 1.0.0
Priority:	Minor
Reporter:	yang shi

In Jira workflow, I have added two states: 修改中, 待测试验证. Then in my jenkins job, I set up the changelog matcher. After I updated the Jira issue workflow status, I have seen the Webhook message in Jenkins, but the job didn't be triggered.

In Webhook message, I find the "fromString" is "\u6dc7\ue1bd\u657c\u6d93\ufffd", the “toString“ is "\u5bf0\u546e\u7974\u7487\u66e2\u7359\u7487\ufffd", but I couldn't convert the unicode of these strings to corrected states(Simplified Chinese).

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

wisen@ceilfors.com (JIRA)

unread,

Jun 3, 2019, 4:53:24 PM6/3/19

to jenkinsc...@googlegroups.com

Wisen Tanasa commented on

Have you tried entering the Chinese characters to the "JIRA field Matcher" directly?

I'm guessing that the problem with entering "\u6dc7\ue1bd\u657c\u6d93\ufffd" in the field is, the backslash will be treated as just another String, hence the characters will not be treated as a unicode.

2294649893@qq.com (JIRA)

unread,

Jun 3, 2019, 8:49:02 PM6/3/19

to jenkinsc...@googlegroups.com

yang shi updated an issue

Jenkins /

Change By:	yang shi
Attachment:	image-2019-06-04-08-48-13-492.png

2294649893@qq.com (JIRA)

unread,

Jun 3, 2019, 8:59:02 PM6/3/19

to jenkinsc...@googlegroups.com

yang shi commented on

Thanks Wisen! I have entered the Chinese characters before I asked this question, but it doesn't work. So I guess is it possible the unicode of these Chinese characters maybe incorrect? Then I used a unicode convert tool, the unicode of "修改中" is "\u4fee\u6539\u4e2d" and the unicode of "待测试验证“ is "\u5f85\u6d4b\u8bd5\u9a8c\u8bc1", these are not same with the Webhook message.

wisen@ceilfors.com (JIRA)

unread,

Jun 4, 2019, 1:33:02 AM6/4/19

to jenkinsc...@googlegroups.com

Wisen Tanasa commented on

I'm afraid this plugin has no control over the WebHook message generated from JIRA. I would suggest you to contact the JIRA support or community and see if you can fix the WebHook message. I think there is a bug in JIRA when the string is stored. There are "\ufffd" in both of the strings too.

wisen@ceilfors.com (JIRA)

unread,

Jun 4, 2019, 1:34:03 AM6/4/19

to jenkinsc...@googlegroups.com

Wisen Tanasa commented on

I believe I can't help you further on this one, feel free to re-open if the issue is moved to this plugin.

wisen@ceilfors.com (JIRA)

unread,

Jun 4, 2019, 1:34:03 AM6/4/19

to jenkinsc...@googlegroups.com

Wisen Tanasa closed an issue as Not A Defect

Jenkins /

Change By:	Wisen Tanasa
Status:	Open Closed
Resolution:	Not A Defect

2294649893@qq.com (JIRA)

unread,

Jun 17, 2019, 1:40:02 AM6/17/19

to jenkinsc...@googlegroups.com

yang shi reopened an issue

Hi Tanasa,
I have contacted the JIRA support and the result is that the character encoding in HTTP heads is set to UTF-8 as expected, the JSON payload also shows the correct character, it doesn't look like JIRA is messing up the character encoding.

Jenkins /

Change By:	yang shi
Resolution:	Not A Defect
Status:	Closed Reopened

2294649893@qq.com (JIRA)

unread,

Jun 17, 2019, 1:41:02 AM6/17/19

to jenkinsc...@googlegroups.com

yang shi updated an issue

Jenkins /

Change By:	yang shi
Attachment:	screenshot-0.png

2294649893@qq.com (JIRA)

unread,

Jun 17, 2019, 1:42:01 AM6/17/19

to jenkinsc...@googlegroups.com

yang shi updated an issue

Jenkins /

Change By:	yang shi
Attachment:	screenshot-2.png

2294649893@qq.com (JIRA)

unread,

Jun 17, 2019, 1:42:02 AM6/17/19

to jenkinsc...@googlegroups.com

yang shi updated an issue

Jenkins /

Change By:	yang shi
Attachment:	screenshot-1.png

2294649893@qq.com (JIRA)

unread,

Jun 17, 2019, 1:43:02 AM6/17/19

to jenkinsc...@googlegroups.com

yang shi edited a comment on

Hi Tanasa,
I have contacted the JIRA support and the result is that the character encoding in HTTP heads is set to UTF-8 as expected, the JSON payload also shows the correct character, it doesn't look like JIRA is messing up the character encoding.

Please see the new images I have uploaded. Thanks!

wisen@ceilfors.com (JIRA)

unread,

Jun 17, 2019, 3:20:01 PM6/17/19

to jenkinsc...@googlegroups.com

Wisen Tanasa commented on

Thanks for getting back to this issue. I'm a little tight on my capacity at the moment and it's going to take sometime (few weeks) before I can have start looking into this issue. Feel free to contribute to the project though!