Check acceptance criteria in a code review

With code reviewer, Rovo Dev can compare the code in your pull request to requirements listed in your linked Jira work items.

Rovo Dev will let you know whether the acceptance criteria it has found:

• Are successfully met.

• Are missing from the code.

• Need manual checking.

How to write your acceptance criteria

Rovo Dev will check for acceptance criteria in the summary, description, and custom fields of work items linked to the pull request.

For Rovo Dev to find acceptance criteria, you must label them with:

• "Acceptance Criteria", "AC", or "ACs".

• "Business Requirements", "Functional Requirements", or "Requirements".

• "Definition of Done" or "DoD".

Rovo Dev works best with acceptance criteria that are:

• Short and focused on one specific thing.

• Written in clear, unambiguous language.

• Describe success in measurable, positive terms.

Use Atlassian Intelligence to turn your brainstormed thoughts into clear, structured work item descriptions.

Once you find a format and structure that works for your team, use it as a template so you can quickly reuse it for all your work items.

Enable or disable acceptance criteria checks

Acceptance criteria checks for code reviews are enabled by default.

In Bitbucket

To turn acceptance criteria checks off or on for your Bitbucket repository:

1. Go to Repository Settings for your repository.

2. Select Code Reviewer from the side panel.

3. Turn Acceptance criteria check on or off.

In GitHub

1. Go to https://{your-site-name}.atlassian.net/dev-agents/

2. Under Code Reviewer, select Enable Code Reviewer on repositories.

3. Select GitHub, then Manage repositories from the list of organizations.

4. Select Manage settings from the list of repositories.

5. Turn off Acceptance criteria check on or off.