Hmm, thanks for your answer but that's only partially true.
It is true when the whole plan was triggered manually (by clicking on "Run" button). However, my case is different:
In my plan there are two stages:
* first stage is triggered by SVN change. I don't run it manually.
* the second stage is a manual stage - it requires a user to click on "Run" button.
The problem is that when the first stage is triggered automatically by SVN commit and after that a user starts the second stage manually - I can't find out who started it. There's no "ManualBuildTriggerReason.userName" key in jobs' metadata.
Could it be a bug/missing feature?
Seems to be driven by the Triggers (manual vs scheduled vs repo-generated). If I do a Manual build by clicking run build then the property I mentioned is in the metadata tab. If I have a scheduled build or one of the other trigger types it seems like it doesn't record the user who manually runs the Manual Stage that is paused. I would argue that is a bug (the ManualBuildTriggerReason.userName or at least some other piece of similar metadata) should be captured when a user manually continues a paused Stage.
On 31 May, a GDPR-related change went live in the Bitbucket Cloud API that resulted in users not being able to create or edit Bitbucket Cloud Linked repositories in Bamboo. This API update removed t...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events