Our Azure DevOps pipelines are configured for bidirectional sync with Rally defect-tracking. When developers mark defects as Fixed in Azure and the pipeline completes, Rally defects remain in their original status (usually Submitted or Open).
The Azure pipeline shows successful completion and the Rally connector extension reports no errors. We can see the ExternalID field in Rally populated with the Azure work item ID, but status updates don’t flow back. The workspace subscription appears active and the ObjectID correlation looks correct.
This is impacting our sprint velocity reporting since Rally doesn’t reflect actual defect resolution. Has anyone resolved state transition issues between Azure DevOps and Rally’s defect management?
We had this exact issue last quarter. The problem was our workspace subscription was configured to only sync defect creation events, not status updates. Go to Rally Setup > Integrations and check your Azure DevOps subscription settings. Make sure “Defect Status Updates” is enabled in the event types. Also verify the subscription scope includes all workspaces where your defects exist.
Check your Azure DevOps service connection permissions in Rally. Even if the subscription is configured correctly, the service account might not have rights to transition defects through certain states. Rally 2024 has stricter role-based access control for state transitions. The account needs both read and write permissions on the defect-tracking module plus explicit workflow transition rights.
I checked the subscription settings and status updates are enabled. Here’s our current mapping:
{"azure_state":"Done","rally_state":"Fixed",
"externalID":"AB#12345",
"objectID":"defect/987654"}
The Azure connector shows this mapping in the sync logs, but Rally still shows the defect as Open. Could this be an ObjectID correlation problem where Rally isn’t matching the incoming update to the existing defect?