• 1
    • 3
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      When a Plan is run manually it obviously logs who triggered it in the build result summary/history, but also there is a MetaData tab that contains the property "ManualBuildTriggerReason.userName" with a value of the user who triggered it.

      If a Plan contains a Stage that is marked MANUAL then when that Plan is triggered in a non-manual way, say single daily build, VCS polling, or cron expression the plan runs, pauses at the Manual Stage, and waits for someone to continue the paused Manual Stage. This is a MANUAL action a user must take, thus the person who performed the action should get logged, but it does not, plus the ManualBuildTriggerReason.userName property doesn't get created/logged even though the Manual Stage was manually continued by userX. Whether it is that property or another one it seems the user who continues the Manual Stage should get logged somehow.

            [BAM-12858] Logging Who Triggered a Manual Stage

            Atlassian Update - 27 April 2025

            Hello,

            Thank you for submitting this suggestion. We appreciate you taking the time to share your ideas for improving our products, as many features and functions come from valued customers such as yourself.

            Atlassian is committed to enhancing the security and compliance of our Data Center products, with an emphasis on sustainable scalability and improving the product experience for both administrators and end-users. We periodically review older suggestions to ensure we're focusing on the most relevant feedback. This suggestion is being closed due to a lack of engagement in the last four years, including no new watchers, votes, or comments. This inactivity suggests a low impact. Therefore, this suggestion is not in consideration for our future roadmap.

            Please note the comments on this thread are not being monitored.

            You can read more about our approach to highly voted suggestions here and how we prioritize what to implement here.

            To learn more about our recent investments in Bamboo Data Center, please check our public roadmap.

            Kind regards,
            Bamboo Data Center

            Aakrity Tibrewal added a comment - Atlassian Update - 27 April 2025 Hello, Thank you for submitting this suggestion. We appreciate you taking the time to share your ideas for improving our products, as many features and functions come from valued customers such as yourself. Atlassian is committed to enhancing the security and compliance of our Data Center products, with an emphasis on sustainable scalability and improving the product experience for both administrators and end-users. We periodically review older suggestions to ensure we're focusing on the most relevant feedback. This suggestion is being closed due to a lack of engagement in the last four years , including no new watchers, votes, or comments. This inactivity suggests a low impact. Therefore, this suggestion is not in consideration for our future roadmap. Please note the comments on this thread are not being monitored. You can read more about our approach to highly voted suggestions here and how we prioritize what to implement here. To learn more about our recent investments in Bamboo Data Center, please check our public roadmap . Kind regards, Bamboo Data Center

            This feature is essential if Bamboo is to support Continuous Delivery pipelines in an environment where auditing who did what is important.

            Can you please confirm if you have any plans to actually implement this?

            It's lack of support for this kind of feature that makes Jenkins or Go a much more attractive proposition than Bamboo for serious CD pipelines.

            David Genn added a comment - This feature is essential if Bamboo is to support Continuous Delivery pipelines in an environment where auditing who did what is important. Can you please confirm if you have any plans to actually implement this? It's lack of support for this kind of feature that makes Jenkins or Go a much more attractive proposition than Bamboo for serious CD pipelines.

            Version 5.7.2 is still affected by this issue

            Sh4kE r0cKz added a comment - Version 5.7.2 is still affected by this issue

            Craig Otis added a comment -

            James, any updates? This continues to impact us nearly a year later.

            Craig Otis added a comment - James, any updates? This continues to impact us nearly a year later.

            This is pretty important for us, any updates?

            Xabier Davila added a comment - This is pretty important for us, any updates?

            Craig Otis added a comment -

            James, is there an alternative metadata property/variable that we can use to determine who triggered a manual build stage, when the build was not started manually?

            ie. We check in code, and the build is triggered automatically. Then we want to run a manual stage at the end to deploy the build to a QA environment. Can we access the username of the person who triggers that manual stage?

            Craig Otis added a comment - James, is there an alternative metadata property/variable that we can use to determine who triggered a manual build stage, when the build was not started manually? ie. We check in code, and the build is triggered automatically. Then we want to run a manual stage at the end to deploy the build to a QA environment. Can we access the username of the person who triggers that manual stage?

            Yep, we should write this out to the log at least. Thanks for filing.

            James Dumay added a comment - Yep, we should write this out to the log at least. Thanks for filing.

              Unassigned Unassigned
              ef602377c686 Adam Myatt
              Votes:
              25 Vote for this issue
              Watchers:
              23 Start watching this issue

                Created:
                Updated:
                Resolved: