Bitbucket Cloud · Data Center · Pull requests · October 26, 2026

Bitbucket pull request tasks

A task is a to-do on a pull request: "add a test", "update the changelog". It can stand on its own or hang off a comment, it is resolved when done, and a merge check can hold the pull request back while any is open. Bitbucket Cloud and Bitbucket Data Center both have tasks and default tasks, but they store and configure them differently. Below is how, from Atlassian's Review code in a pull request and Suggest or require checks before a merge (Cloud), Commenting on a pull request, Default tasks and Checks for merging pull requests (Data Center 10.5), and the two REST references.

Bitbucket Cloud

• Creating a task: from a comment, highlight the text that should become the task and select Create task, or select Create task under the comment, type the task and Save. Anyone with read access can make a task from someone else's comment. For a task on the whole pull request, use Create a task at the bottom of the Task card in the right sidebar.
• Who does what: Atlassian's page says reviewers can create tasks and resolve them, and the pull request's author and repository admins can edit and delete them.
• Where they show: the Task card in the sidebar lists them (the link icon next to a comment's task jumps to that comment), and the Activity feed on the Overview tab has a Tasks filter.
• The merge check: No unresolved pull request tasks, set per branch or branch pattern under Repository settings > Branch restrictions. Without the Premium plan an unmet check only warns, and people can still merge; with Premium, Prevent a merge with unresolved merge checks stops the merge.
• Default tasks: Repository settings > Default tasks (announced July 2022). They are added to every new pull request; a change to the list applies to later pull requests, and pull requests that already have the tasks keep them. Up to 50 default tasks per repository, and 100 tasks per pull request, counting tasks on comments too. They can only be set in the web page: a request for an API, BCLOUD-22783 ("Add API for Pull Request Default Tasks", July 2023), was still Gathering Interest on October 26, 2026.
• From the REST API: GET …/2.0/repositories/{workspace}/{repo_slug}/pullrequests/{id}/tasks lists them (up to 100 a page, sortable and filterable with sort and q, oldest first by default). POST …/tasks creates one with {"content": {"raw": "…"}}, optionally with "comment": {"id": …} to put it under a comment. PUT …/tasks/{task_id} with {"state": "RESOLVED"} resolves it and "UNRESOLVED" reopens it; DELETE removes it. A task carries state, content, creator, resolved_by, resolved_on and pending (a task in a review that is not published yet).
• Task ids are 64-bit. On public repositories they were already above two billion in October 2026, close to the largest signed 32-bit number (2,147,483,647), so a script that reads them into a 32-bit integer is near its end.

Bitbucket Data Center

• Creating a task: on the whole pull request, a file, a line or several selected lines, write the text and select Create task. A comment can be turned into a task and a task back into a comment. Tasks take Markdown, images and attachments. Tasks written while a review is in progress stay pending, visible only to you, until the review is published.
• Resolving: tick the checkbox next to the task. Shift+T or Open tasks list shows the open and resolved tasks, each with a View on link to where it was made.
• A task is a comment. Since Bitbucket 7.0 a task is a comment with BLOCKER severity. The old /tasks REST resources were deprecated in 7.2 and answer 404 from 8.0; use the comment resources instead: …/pull-requests/{id}/blocker-comments lists them (states=OPEN or RESOLVED, count=true for the numbers only), and PUT …/comments/{commentId} with the comment's version and "state": "RESOLVED" resolves one ("OPEN" reopens it), and "severity": "BLOCKER" or "NORMAL" turns a comment into a task or back. The REST reference says only a comment's author can change its text, and only that author, the pull request's author or a repository admin can change its other fields.
• The merge check: No incomplete tasks ("requires all tasks to be complete before merging"), under Project settings > Merge checks for the whole project or Repository settings > Merge checks for one repository.
• Default tasks: Project settings or Repository settings > Default tasks > Add a default task. Each one can be limited to a source and a target branch, or Any branch for both. They are added when a pull request is opened, by the user "Bitbucket", and updated when the pull request's target branch changes. A project's default tasks apply to all its repositories, which can add their own but cannot remove the project's. Edits apply to pull requests opened afterwards; a deleted default task stays on the pull requests that already have it.
• Default tasks from the REST API: …/rest/default-tasks/latest/projects/{projectKey}/tasks and …/projects/{projectKey}/repos/{repositorySlug}/tasks, with GET, POST, PUT and DELETE; changing them takes project or repository admin. A default task's sourceMatcher and targetMatcher are any branch, a branch, a pattern, or a branching model category or branch.

Tasks in IntelliJ IDEA

Pull Request Inbox for Bitbucket, a plugin by Lesstep for JetBrains IDEs 2024.1 or later, lists the Bitbucket Cloud and Bitbucket Data Center pull requests waiting for your review in an IDE tool window. From version 1.0.40 a pull request's overview shows its tasks above the merge checks, "Tasks (1 of 3 resolved)", open ones first, each resolved one with who resolved it; on Data Center these are the comments marked as tasks. Before 1.0.40, Bitbucket Cloud tasks did not show at all, though the merge check can wait for them. Seeing the tasks and the merge checks is free; resolving and reopening a task, like approving, commenting and merging, is Pro, with a 30-day trial.

Get it on JetBrains Marketplace

Bitbucket is a trademark of Atlassian Pty Ltd; IntelliJ IDEA is a trademark of JetBrains s.r.o. This page is not affiliated with or endorsed by Atlassian or JetBrains.

More: merge checks · resolving comments · default reviewers · Request changes and Needs work · builds · 日本語