Request path contains unescaped characters

[김민수]

I'm using JIRA in Korean. The custom field is also set, and all user names are in Korean.

When updating an issue, sometimes I get a 'Request path contains unescaped characters' error. When checked on JIRA web, the updates are as requested.

If necessary, I will add a procedure that can be reproduced.

[김민수]

It is not what I mentioned, but need escape too

‌

[Gregory Star]

Correct me if I’m wrong, but it sound like you’re describing two separate issues: the first is that you’re getting errors when updating an issue, and the second is that you’re getting an error when editing a JQL.

For the second error, the query that you’ve shown causes an error on my end too. Is the status you’re looking for named '/'? If so, you could wrap it in quotation marks like the editor suggests.

For the first problem, if you have a way of helping us reproduce this, that would be very helpful. I can also point you to our standard procedure of enabling curl logging to give more detailed error output if necessary.

‌

[김민수]

It would be two separate issues. I thought the two issues were similar because they were caused by not being unescape.

I found reproducing path: input multibyte(Korean) Assignee field to make autocomplete. (You can copy&paste 김 )

‌

[김민수]

For the first comment:

I think it would be difficult for you to input Korean characters, so I reproduced them with slash (/) characters. I think you are confused because of that.

If you use Korean characters, you will get unescape error even if you enclose the single quotes (').

You can also copy&paste ' 김 '

If this issue is separate from the above, I’ll create a new issue.

‌

[Pramod Busam]

@김민수 For the Edit JQL error, could you try entering the unicode character (status in "\uAE40") and let us know if that works?

We are looking into the issues with other fields like assignee. Could you answer a couple of questions to help us investigate: - Are you using Jira cloud or self-hosted Jira? - Does the issue display correctly with the right assignee after the error is shown? Or if you close and open the issue again?

[Pramod Busam]

Linked to VSCODE-842

[김민수]

@{557058:a30b5736-f3cf-41d7-aad0-99c9ffac78ce}

1. I’m using self-hosted Jira
2. The assignee error seems to occur when requesting data for autocomplete. After I chose assignee, everything works fine.
3. same as number 2.

‌

‌

[김민수]

It works with escaped unicode string.

‌

[Pramod Busam]

Thanks for checking. I was able to reproduce both the JQL input and autocomplete search issues. We'll let you know once it is fixed.

[Pramod Busam]

Version 2.2.0 of the extension fixes this issue.

[Alastair Wilkes]

Removing component: triaged (automated comment)