• Type: Bug
• Resolution: Fixed
• Priority: Low
• Fix Version/s: 3.3.0
• Affects Version/s: 3.2.6
• Component/s: Automation, Request Type Configuration
• Labels:

  • affects-server

1. 

   automation-edit.png

   29 kB

   05/Jan/2017 10:03 AM

2. 

   issue-nav.png

   17 kB

   05/Jan/2017 10:02 AM

[JSDSERVER-4623] When searching using Customer Request Type, characters change to a non user friendly form

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

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

Owen made changes - 24/Oct/2018 5:23 AM

Symptom Severity

Original: Minor [ 14432 ]

New: Severity 3 - Minor [ 15832 ]

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

Workflow

Original: JSD Bug Workflow v5 [ 2059064 ]

New: JSD Bug Workflow v5 - TEMP [ 2305136 ]

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

Workflow

Original: JSD Bug Workflow v5 - TEMP [ 2056459 ]

New: JSD Bug Workflow v5 [ 2059064 ]

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

Workflow

Original: JSD Bug Workflow v5 [ 1955345 ]

New: JSD Bug Workflow v5 - TEMP [ 2056459 ]

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

Workflow

Original: JSD Bug Workflow v4 [ 1635779 ]

New: JSD Bug Workflow v5 [ 1955345 ]

Nhi Nguyen (Inactive) made changes - 09/Jan/2017 1:27 AM

Fix Version/s		New: 3.3.0 [ 61746 ]
Resolution		New: Fixed [ 1 ]
Status	Original: Untriaged [ 11672 ]	New: Done [ 10044 ]

Confluence Escalation Bot (Inactive) made changes - 06/Jan/2017 12:04 AM

UIS - Server

New: 1

Mahmoud Alaaeldin (Inactive) made changes - 05/Jan/2017 10:10 AM

Description

Original: h3. Summary When searching for issues using "Customer Request Type" or editing a condition in an Automation rule using "Customer Request Type", the result turns into non-user friendly characters. h3. Steps to Reproduce # Create a Service Desk project (or navigate to an existing one) # Go into the Service Desk project settings # Create a Request Type - > <give it a name> # Go to issue navigator -> search for issues (Customer Request type = <given name>). # And also try to search for it under the Automation Rule by editing a condition. h3. Expected Result # The search should return the actual Request Type name h3. Actual Result # The request type is returned in the following format: #* When searching from Issue Navigator using this as an example -> "Customer Request Type" = help and support  !issue-nav.png|thumbnail! #* When editing an automation rule using the same JQL query -> "Customer Request Type" = help and support  !automation-edit.png|thumbnail! h3. Workaround No current known workaround h3. Observations In previous versions of ServiceDesk (3.0.x), searching for Request Type was done using this format -> "project-key/lowercased-form-requesttype-title-hyphenated", however in later versions (3.2.x) an Autocomplete function was introduced when searching for Request Types after which I believe this issue started happening

New: h3. Summary When searching for issues using "Customer Request Type" or editing a condition in an Automation rule using "Customer Request Type", the result turns into non-user friendly characters. h3. Steps to Reproduce # Create a Service Desk project (or navigate to an existing one) # Go into the Service Desk project settings # Create a Request Type - > <give it a name> # Go to issue navigator -> search for issues (Customer Request type = <given name>). # And also try to search for it under the Automation Rule by editing a condition. h3. Expected Result # The search should return the actual Request Type name h3. Actual Result # The request type is returned in the following format: #* When searching from Issue Navigator using this as an example -> "Customer Request Type" = help and support  !issue-nav.png|thumbnail! #* When editing an automation rule using the same JQL query -> "Customer Request Type" = help and support  !automation-edit.png|thumbnail! h3. Workaround No current known workaround h3. Observations In previous versions of ServiceDesk (3.0.x), searching for Request Type was done using this format -> "*_project-key/lowercased-form-requesttype-title-hyphenated_*", however in later versions (3.2.x) an Autocomplete function was introduced when searching for Request Types after which I believe this issue started happening

Mahmoud Alaaeldin (Inactive) made changes - 05/Jan/2017 10:10 AM

Description

Original: h3. Summary

New: h3. Summary When searching for issues using "Customer Request Type" or editing a condition in an Automation rule using "Customer Request Type", the result turns into non-user friendly characters. h3. Steps to Reproduce # Create a Service Desk project (or navigate to an existing one) # Go into the Service Desk project settings # Create a Request Type - > <give it a name> # Go to issue navigator -> search for issues (Customer Request type = <given name>). # And also try to search for it under the Automation Rule by editing a condition. h3. Expected Result # The search should return the actual Request Type name h3. Actual Result # The request type is returned in the following format: #* When searching from Issue Navigator using this as an example -> "Customer Request Type" = help and support  !issue-nav.png|thumbnail! #* When editing an automation rule using the same JQL query -> "Customer Request Type" = help and support  !automation-edit.png|thumbnail! h3. Workaround No current known workaround h3. Observations In previous versions of ServiceDesk (3.0.x), searching for Request Type was done using this format -> "project-key/lowercased-form-requesttype-title-hyphenated", however in later versions (3.2.x) an Autocomplete function was introduced when searching for Request Types after which I believe this issue started happening

Load more older history items