Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

During Blackout period is there warning or banner to enable in the Pull request before approval.

During Blackout period is there warning or banner can be enabled in the Pull Request before it get approved.

1 answer

0 votes
Mark C Atlassian Team Jan 24, 2023

Hi @Raja Suresh

When you mentioned "blackout period", would it be possible for you to confirm which blackout period you're referring to?

Are you referring to incidents/outages on our end?
If yes, we do add a banner on when there is an ongoing incident/outage on our end. This way, users will be notified on the UI about it.

Mark C

@Mark C , Thanks for the response.

There is there period in our organization last 2 weeks(blackout period) of every quarter we should not approve some part of sustaining Pull Request unless if it is very urgent and important to approve. So we are expecting some kind of warning during that period.

Mark C Atlassian Team Jan 26, 2023

Hi @Raja Suresh,

Unfortunately, there's no option in Bitbucket Cloud Pull requests to customize the view to add a banner or notification.
This feature was being tracked as a suggestion in BCLOUD-20745, but we have made the decision not to implement this feature and closed the suggestion.

This decision was made to be transparent about future features under consideration. You can see more details regarding the decision in this comment

As a possible workaround, to prevent a pull request from being merged, you can explore implementing branch permissions by manually adding/removing it based on your preferred period.

Do let me know if you have further questions that can help with.

Mark C

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events