-
-
Notifications
You must be signed in to change notification settings - Fork 131
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
Fix email notification not sending #384
Conversation
Commenting from my phone here. But you must also change the notify param to String and value "true" FROM TO |
@skuzzles, can you explain why it should be a string? I agree that there might be a better way to do this, particularly with @replicaJunction's idea to identify default behavior and use a switch parameter to change it. But, adjusting the data type would be a functionality change, potentially breaking existing automation. The fix I submitted has been tested to resolve the issue and keeps this in the 'bug fix' category. |
@skuzzles if ($Notify) {"true"} else {"false"} but not to allow the user to type any string @johnheusinger |
@lipkau Yup, tested it manually |
Atlassian documentation states the notification property is a string. "true" is default and "false" is accepted alternative. The reason @johnheusinger suggestion works is because it is defaulting to true, since the property is now successfully changed from notify to notification. If you've tested it manually, try testing it with -Notify false to see if you do not receive a notification. |
@johnheusinger : can you please test it with |
@lipkau I tested the following cases: Without |
Description
Changed 'notify' to 'notification' in the request body to align with API documentation
Motivation and Context
Closes issue #382
Types of changes
Checklist