This was something discussed in PM-794 but ruled out of scope. From the design doc:
Running downstream tasks in patches will be added as a later feature outside this epic, if there is sufficient interest in such a feature
- A boolean flag will be added to the CLI patch command as well as the patch UI to run any downstream builds that would happen (default is to not run these).
- The downstream tasks will be displayed in a separate section within the same patch.
- The /patches endpoint will return the downstream tasks as part of the patch that triggered them.
- Each downstream build triggered in this manner will have a patch created in the corresponding project. The patch will have no diff and will have a reference to the patch that triggered it. The expansions mentioned above will be populated accordingly.
Another addition to the above is that for pull requests the additional tasks should behave as if they were part of the main patch definition