-
Notifications
You must be signed in to change notification settings - Fork 327
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
escape or sanitize inputs #115
Comments
The
It needs to use the multiline block yaml notation like:
I will get this change in. For the JQL issue, that is hard to do the escaping generically. I would argue that it is a problem with your query string rather than an issue with I would rewrite you command like:
then the usage would be |
Great. I like the solution for the custom command options. Thanks! |
I have updated the default template and cut a release: Hopefully that fixes your escaping issues with the description field. |
Fields to and from Jira can have any type of formatting. These fields should be escaped before being placed in the YAML templates.
For example:
Results in:
In this case the description should be wrapped in parenthesis and if the story includes any special characters they should be escaped. Having to do this manually is cumbersome.
This is also true for custom commands and arguments.
For example:
The text was updated successfully, but these errors were encountered: