Brandon Reppert Atlassian Team

Hey Kristin, thanks for raising this. We'd certainly like to implement a native confluence search experience for that field, but the implementation is going to be a little different from projects because we aren't going to assume that all of your documentation lives in Confluence, whereas project refers specifically to a…

Hi @DirkHeinke Unfortunately this webhook will not automatically allow for a Jira automation. We'll need to follow up with the Jira team here. Do you mind elaborating on what your use case for this would be? Thanks, Brandon

Hi @olockwood, glad the feature is proving useful for you. The internal API should be accessible to your team in the same manner that the public API would, but the caveat with internal APIs is that the documentation isn't publicly accessible and we retain the ability to make breaking changes to the API at any time. Let me…

This functionality has been restored (public issue: https://jira.atlassian.com/browse/BCLOUD-20665).

Hi @Sean Lively, thanks for this feedback. I agree with the button text changing when the buttons are selected. We'll have a change out shortly for "Approve" to become "Approved" when set and likewise for "Request changes" to become "Changes requested". We're also considering your feedback for merge button placement for PR…

@rsbeckerca You can add reviewers to a pull request after its created by selecting the expanded actions menu (the meatball just to the right of the approve button) and selecting "Edit". We understand that there are use cases outlined here that utilize the self-approve functionality beyond the work in progress state, and so…

Thanks for the additional input. We believe there are some cached PR states where the self-approval was still an option, which is why it has been sometimes still displaying. Public issue ticket for this created: https://jira.atlassian.com/browse/BCLOUD-20665

@Antonius Golly There is some more information on the new reviewer status here: https://bitbucket.org/blog/a-new-status-for-pull-requests-in-bitbucket-cloud-changes-requested The removal of self-approvals was intended as a part of this change, but to be truthful I believe it was an oversight on our part for how people were…

@Antonius Golly this functionality was removed today as part of our updates adding the "Requests Changes" reviewer status. This was purposefully removed as we were separating the author and reviewer experiences. It sounds like what you are requesting would best be met by having the author able to set an explicit "Work in…

@Tom Somerville Thanks for the info and sorry for the delayed response -- I'm not able to reproduce that bug on my side. I'll take another look after our most recent round of refactors/fixes to see if I'm able to reproduce what you're seeing.

Thanks @raijinsetsu! We recently released a pretty major refactor that unfortunately broke some functionality, but we have a fixed version ready to go that should be out soon. Let us know if your issue persists (especially if it persists into next week).

@Chris Fouts Noted -- I agree it definitely would be useful to have the feature able to schedule the pending merge to complete as soon as all merge checks are passed. However as it's currently set up it's a feature specifically against builds, and would need somewhat significant changes to check against all the different…

We have fixed the issue related to the functionality not being available in cases where it should have been enabled. Thanks again for everyone that raised the issue here. Anyone who was having difficulties scheduling pending merges should be able to re-try using the feature now and let us know if you have any continued…

@Brandon Poe @Chris Fouts You can cancel the merge by clicking the "Merge" button again and then selecting "Cancel Merge" on the modal. On a separate note, we have discovered the source of the bug that we believe is the root cause for the above issues. It's related to how we gated the feature as a labs feature making the…

Those screenshots are helpful, thanks @Jack Gersten! You definitely have the right configuration and there's a bug here. @Roman Panchenko I'll add some details to our internal bug ticket. I see some inconsistent logic applied in the modal that should give us an idea of what's going on here. Thanks everyone for your reports…

@Chris Fouts Yes that's definitely it, sorry for the confusion. Pending merges is specifically for scheduling automatic merging against builds. It's not designed to automatically merge the request as soon as all of the merge checks pass. It'd definitely be useful to have the option for the merge to go through as soon as…

@Tim Peeters We were unable to reproduce the issue ourselves on a free account. Could you provide some more details for your configuration, either here or by opening a BCLOUD ticket at https://jira.atlassian.com/secure/Dashboard.jspa. If you do open a BCLOUD ticket please let me know here and mention me on the ticket so I…

@Tim Peeters Thanks for letting us know. I think it's definitely possible that the feature isn't working properly on non-premium accounts, though we intended the functionality to be available to non-premium users. We'll try to reproduce and fix the issue. @Chris Fouts I'm sorry to hear that the feature didn't work for you.…