We have several pipelines set such that the fist stage is a manual approval. We also have setup to trigger with options. I have noticed that the source update is not happening correctly. It appears the build is being executed witht he last revision run if the "revision to trigger with" is left empty.
I would have expected the most recent revision to execute rather than defaulting to the last revision run.
If I trigger with options from an upstream pipeline the behaviour is as I would expect.