-
Type:
Suggestion
-
Resolution: Unresolved
-
Component/s: Alerts - Attachments / Notes, Alerts - Status / Details
-
None
-
0
User Problem
In the current design, the delimiter, comma for example, in the URL will be considered and parsed as part of the URL value, which could lead to a 404 error especially if the URL contains an object ID at the end.
Suggested Solutions
Please change the behavior for not taking the delimiters into the URL parsing.
Current Workarounds
Make a script or alert policy to avoid any delimiters, but it's difficult and extra effort for customization especially since the default nature of Jira Automation is using delimiters to separate the items.