Automatically decline inactive pull requests
Administering Bitbucket Server
- Users and groups
- External user directories
- Global permissions
- Setting up your mail server
- Integrating Bitbucket Server with Atlassian applications
- Connecting Bitbucket Server to an external database
- Migrating Bitbucket Server to another server
- Run Bitbucket in AWS
- Specifying the base URL for Bitbucket Server
- Configuring the application navigator
- Managing apps
- Auditing in Bitbucket
- Updating your Bitbucket Server license details
- Bitbucket Server config properties
- Moving Bitbucket Server to a different context path
- Data recovery and backups
- Disabling HTTP(S) access to Git repositories in Bitbucket Server
- Smart Mirroring
- Data Center Migration
- Git Large File Storage
- Git Virtual File System (GVFS)
- Enabling SSH access to Git repositories in Bitbucket Server
- Using diff transcoding in Bitbucket Server
- Changing the port that Bitbucket Server listens on
- Lockout recovery process
- Proxying and securing Bitbucket Server
- High availability for Bitbucket
- Diagnostics for third-party apps
- Enabling JMX counters for performance monitoring
- Bitbucket Server debug logging
- Scaling Bitbucket Server
- Add shortcut links to a Bitbucket Server repository
- Administer code search
- Adding additional storage for your repository data
- Add a system-wide announcement banner
- Configuring Project links across Applications
- Improving instance stability with rate limiting
- Use a CDN with Atlassian Data Center applications
- Managing personal access tokens
- Connecting to a 3rd party application using Application Links
- Setting a system-wide default branch name
- Automatically decline inactive pull requests
On this page
Related content
- Migration of Templates from Wiki Markup to XHTML-Based Storage Format
- Upgrading from 3.5 to 5.1 - Upgrade Notes
- Upgrading from Confluence 3.5 to 5.1 - Simplified Guide
- Convert Wiki Markup Pages That Fail to Convert from Wiki Markup to XHTML
- Confluence logs show XHTML exception reports.
- Import Content Into Confluence
- Upgrading Confluence
- Memory Usage and Requirements
- Upgrading Confluence Manually
- Upgrade Confluence without downtime
Bitbucket Server and Data Center will automatically decline pull requests that are inactive, reducing the number of pull requests in the list that can add up. For example, if an older pull request has not had any activity (like commits, comments or approvals) in a set amount of time, it will be declined. By default, the option is on and set to 4 weeks. This period of inactivity can be overwritten for projects and repositories.
There is an instance-wide configuration property for this feature in the bitbucket.properties file that allows admins to disable or turn the feature off.
feature.pull.request.auto.decline=falseAutomatically decline inactive pull requests for all repositories in a project
To configure the automatic declining of inactive pull requests in a project:
Select Project settings > Auto-decline.
Select the Auto-decline pull requests check-box to enable it.
Set the amount of time before a pull request will be automatically declined from 1, 2, 4, 8, or 12 weeks.
Select Save.
Automatically decline inactive pull requests for a repository
Configuring this setting at the repository level, will override the setting for it at the project level.
To configure the automatic declining of inactive pull requests in a single repository:
Select Repository settings > Auto-decline.
By default, settings are inherited from the project settings.
Select Use custom settings.
Select the Auto-decline pull requests check-box to enable it.
Set the amount of time before a pull request will be automatically declined from 1, 2, 4, 8, or 12 weeks.
Select Save.
Once the configuration is saved, inactive pull requests will become declined by the Bitbucket system user. This will add a comment indicating that the reason for the decline is due to inactivity.
Related content
- Migration of Templates from Wiki Markup to XHTML-Based Storage Format
- Upgrading from 3.5 to 5.1 - Upgrade Notes
- Upgrading from Confluence 3.5 to 5.1 - Simplified Guide
- Convert Wiki Markup Pages That Fail to Convert from Wiki Markup to XHTML
- Confluence logs show XHTML exception reports.
- Import Content Into Confluence
- Upgrading Confluence
- Memory Usage and Requirements
- Upgrading Confluence Manually
- Upgrade Confluence without downtime