Issue Summary

That's not possible to create customized policies with Terraform module atlassian-operations_notification_policy because it doesn't accept startDay and endDay parameters in the timeRestrictions.

We noticed this is a missing documentation information in the Operations API, however, these parameters are still working.

We have another bug ticket to adjust the documentation: JSDCLOUD-17705.

Steps to Reproduce

1. Try to use the Terraform module atlassian-operations_notification_policy to create a new policy;
2. That's not possible to set a customize time restrictions date.

Expected Results

We should be able to set the time restrictions with startDay and endDay, as we did in the Opsgenie API and in the UI.

That's is still possible to use the parameters, but it is not documented.

Actual Results

As this is not documentation, this is causing confusion for our customers. The startDay and endDay parameters are still working in the Operations API.

Workaround

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