[#JRA-14682] Key for additional/custom user property accepts only ASCII characters

JIRA

Key for additional/custom user property accepts only ASCII characters

Created: 20/Mar/08 01:24 AM Updated: 09/Apr/08 11:36 PM

Component/s:

User Management

Affects Version/s:

None

Fix Version/s:

None

Time Tracking:

Not Specified

Issue Links:

Reference

This issue is related to:

JRA-14779 Misleading error message on custom user key validation

Participants:	Anton Mazkovoi [Atlassian] and Bogdan Dziedzic [Atlassian]
Since last comment:	1 year, 12 weeks, 1 day ago
Labels:

Description

« Hide

Key for additional/custom user property accepts only a combination of the ASCII characters and the numerics.

That could be a problem for some customers requiring use of characters from other languages for their keys.
On the top of that they will get also a useless error message "The ''key'' can only contain alphanumeric characters."

public class
        EditUserProperties extends UserProperty
{
    private static final Pattern PATTERN = Pattern.compile("[a-zA-Z0-9\\s]+");

All

Comments

Work Log

Change History

Sort Order:

[ Permalink | « Hide ]

Anton Mazkovoi [Atlassian] added a comment - 24/Mar/08 07:01 PM

We keep the keys in ASCII characters on perpose, as this is usually a good idea. Doing so avoids encoding problems down the track.

The values should allow any characters.

[ Permalink | « Hide ]

Anton Mazkovoi [Atlassian] added a comment - 24/Mar/08 07:01 PM

If this is really needed, please explain why the key cannot be restricted to ASCII characters.

[ Permalink | « Hide ]

Bogdan Dziedzic [Atlassian] added a comment - 08/Apr/08 01:17 AM

There are two separate part to this issue.

The first one - JIRA is used by customers from different countries where either they use extend ASCII characters (Europe) or don't use it at all (Asia).
We already allow to use not ASCII characters for all sort of fields in JIRA and it works OK, so why this filed is different.

Anyway, I can imagine two cases where this can be a problem:
1. Customer from an Asian country that doesn't use ASCII at all wants to store some extra property for his users. How that would can be done?
2. People in Europe intend to use their own languages (extended ASCII) and would love to use their own language script rather than "the English script".

After all we sell JIRA to customers from all over the word and English is not the only language in use by them.

The second one is the misleading error message that doesn't say that we refer to ASCII characters - The ''key'' can only contain alphanumeric characters.

PS. This issue was based on a case from SAC - https://support.atlassian.com/browse/JSP-21257

[ Permalink | « Hide ]

Anton Mazkovoi [Atlassian] added a comment - 08/Apr/08 11:42 PM

Hi Bogdan,

Thanks for the update. Could you give me the error message that the user currently shows.

Cheers,
Anton

[ Permalink | « Hide ]

Bogdan Dziedzic [Atlassian] added a comment - 08/Apr/08 11:45 PM

The error message that is displayed in the UI is:

The ''key'' can only contain alphanumeric characters.

[ Permalink | « Hide ]

Anton Mazkovoi [Atlassian] added a comment - 09/Apr/08 11:36 PM

I have created bug JRA-14779 for correcting the error message.

I forgot that the keys of user properties actually appear in the interface. So it would be useful if they allowed international characters. Therefore, I will reopen this issue.

However, I am not sure if there are no technical problems with this. We will need to investigate if this issue is scheduled.