Webhook does not fire for specific projects during Initiative updates (Rally)

Products

• Rally SaaS

Issue/Introduction

You experience a scenario where webhooks do not fire for certain projects when you update an Initiative in Rally. While the webhook fires correctly for most projects, it fails for specific ones even when required attributes like Planned Start Date, Planned End Date, and Portfolio Type are correctly populated

Cause

The issue occurs because the Project Name in Rally does not exactly match the Project Name in the target system (such as Clarity). In this case, an extra space in the project name configuration prevents the webhook from firing as expected 

Resolution

To resolve this issue, you must ensure that the project names are identical across both systems:

1. Review the Project Name configuration in Rally.
2. Compare it against the project name in the target system (e.g., Clarity).
3. Remove any leading, trailing, or extra internal spaces in the project names.
4. Verify that all characters, including invisible white spaces, match exactly between the systems Webhook not firing for all projects listed in the file.

Additional Information Check with SE teams for exceptions if the naming convention must differ for specific business requirements. For issues involving integrations between Rally and other Broadcom products, always verify the payload and target URL (e.g., https://####-api.jitterbit.net/####/rallyClarityWebhook) to ensure the connection is active