Issue Summary

The command /jsmops whoisoncall doesn't work as expected when the schedule names have a / (slash) in the name.

Steps to Reproduce

1. Integrate JSM Operations with Slack as per this doc.
2. Run the command /jsmops whoisoncall <Schedule-Name> where <Schedule-Name> includes a / (slash).

Expected Results

The command should return the on-call participants for the specified schedule, regardless of any special characters, including slashes, in the schedule name.

Actual Results

• The command /jsmops whoisoncall displays all schedules, even those with a / in their name.
• The command /jsmops whoisoncall <Schedule-Name> where Schedule-Name has special characters like - (dash) works as expected.
• The command /jsmops whoisoncall <Schedule-Name> where Schedule-Name has a / (slash) shows an error like below:

  • ServiceName: schedule Response: { Status: 404 Body: [ {"message":"No handler found","took":0.001,"requestId”:”xxxxxx-xxxx-xxxx-xxxxxx”} ] } Request: { URI: http://og-schedule-int-api.mesh:20027/schedules/schedule%20/%name%20Call/on-calls?customerId=xxxxxxx-xxxxx-xxxx-xxxx&identifierType=name }

     

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available