• Type: Bug
• Resolution: Fixed
• Priority: Low
• Fix Version/s: 1.0.3
• Affects Version/s: None
• Component/s: None
• Labels:

  None

[JSDSERVER-5] Request type with international characters in their name will break in some circumstances

Owen made changes - 27/Mar/2019 5:46 AM

Workflow	Original: JSD Bug Workflow v5 - TEMP [ 2304499 ]	New: JAC Bug Workflow v3 [ 3125421 ]
Status	Original: Done [ 10044 ]	New: Closed [ 6 ]

Katherine Yabut made changes - 06/Jun/2017 3:16 AM

Workflow

Original: JSD Bug Workflow v5 [ 2058661 ]

New: JSD Bug Workflow v5 - TEMP [ 2304499 ]

Katherine Yabut made changes - 31/May/2017 12:38 AM

Workflow

Original: JSD Bug Workflow v5 - TEMP [ 2056463 ]

New: JSD Bug Workflow v5 [ 2058661 ]

Katherine Yabut made changes - 31/May/2017 12:35 AM

Workflow

Original: JSD Bug Workflow v5 [ 1956020 ]

New: JSD Bug Workflow v5 - TEMP [ 2056463 ]

Katherine Yabut made changes - 03/Apr/2017 5:18 AM

Workflow

Original: JSD Bug Workflow v4 [ 1615855 ]

New: JSD Bug Workflow v5 [ 1956020 ]

jonah (Inactive) made changes - 02/Apr/2017 11:38 AM

Description

Original: When a request type is created with international characters in its name, those characters will find their way into the key for that request type. This causes problems in the edit fields screen due to URL character encoding insanity - see http://stackoverflow.com/questions/4028290/encoding-problem-between-jquery-and-java We currently have a hack to get around this (see ServiceDeskURLDecoder.scala), but it only works if JIRA's server.xml has its URIEncoding set to ISO-8859-1 (Latin-1). This is the default, but the edit field screen is likely to break if it has been modified. The hack also doesn't help on IE8 and IE9. We need a more general solution to handle this problem.

New: {panel:bgColor=#e7f4fa}   *NOTE:* This bug report is for *JIRA Service Desk Server*. Using *JIRA Service Desk Cloud*? [See the corresponding bug report|http://jira.atlassian.com/browse/JSDCLOUD-5].   {panel} When a request type is created with international characters in its name, those characters will find their way into the key for that request type. This causes problems in the edit fields screen due to URL character encoding insanity - see http://stackoverflow.com/questions/4028290/encoding-problem-between-jquery-and-java We currently have a hack to get around this (see ServiceDeskURLDecoder.scala), but it only works if JIRA's server.xml has its URIEncoding set to ISO-8859-1 (Latin-1). This is the default, but the edit field screen is likely to break if it has been modified. The hack also doesn't help on IE8 and IE9. We need a more general solution to handle this problem.

jonah (Inactive) made changes - 02/Apr/2017 11:38 AM

Link

New: This issue relates to JSDCLOUD-5 [ JSDCLOUD-5 ]

Katherine Yabut made changes - 19/Oct/2016 6:49 AM

Workflow

Original: JSD Bug Workflow v2 [ 1603042 ]

New: JSD Bug Workflow v4 [ 1615855 ]

Owen made changes - 22/Sep/2016 3:24 AM

Workflow

Original: JSD Bug Workflow [ 1399161 ]

New: JSD Bug Workflow v2 [ 1603042 ]

Owen Sanico [Administrative Account] made changes - 23/May/2016 6:51 AM

Workflow

Original: TTT: Simple Issue Tracking Workflow [ 559961 ]

New: JSD Bug Workflow [ 1399161 ]

Load more older events