Problem

Users attempting to create notification policies for Jira Service Management Operations using the Terraform provider encounter an error indicating an inconsistent result after apply, specifically related to the not field in filter conditions.

Environment

• Terraform Provider: atlassian/atlassian-operations
• Operation: Applying a notification policy configuration
• Platform: Atlassian Cloud (JSM Operations)

Steps to Reproduce

• Use the official atlassian/atlassian-operations Terraform provider.
• Define a notification_policy resource with one or more filter conditions.
• Run terraform apply.

Expected Results

The notification policy should be created successfully, and Terraform should report a consistent state before and after apply.

Actual Results

Terraform throws the following error:

Error: Provider produced inconsistent result after apply

When applying changes to
atlassian-operations_notification_policy.<resource_name>,
provider
"provider[\"registry.terraform.io/atlassian/atlassian-operations\"]"
produced an unexpected new value: .filter.conditions[0].not: was null, but now cty.False.

This suggests that the provider is returning a different internal representation (null → false) after apply, which violates Terraform expectations.

Workaround

(Add a workaround, if available)

Notes