Bamboo-JIRA integration build result propagation timing under load

Measuring a bottleneck before optimizing Bamboo plans requires separating build execution time from integration latency at the Bamboo-JIRA boundary.

The integration relies on REST API calls to transition JIRA issues after a build completes. Behavior may differ between Bamboo Server/Data Center and Bamboo Cloud, and Elastic Bamboo agent startup is deprecated in favor of Bamboo Cloud elastic agents. The central build queue and agent capability matching can introduce queue wait time that is distinct from agent resource contention, and provisioning overhead for short-lived plans is not visible in utilization metrics alone.

It is unclear how build success is reported relative to completion of the JIRA update, and whether propagation delay is observable separately from queue wait time in current releases.

What determines the timing of JIRA issue transition relative to Bamboo build completion?

Under what conditions does Bamboo report build success before the REST transition completes?

Is the propagation delay distinguishable from build queue wait time in Server/Data Center 9.x?