Creating Issues from Review Comments

Every review comment Codity posts on a pull request includes action buttons to turn that finding into a tracked issue with a single click. No copy-pasting, no context switching, the issue is created and linked back to the comment automatically.

Overview

When Codity posts a review comment, each finding includes two issue-creation buttons:

  • Create Issue: creates an issue directly in the native platform (GitHub Issues, GitLab Issues, Bitbucket Issues, or Azure DevOps Work Item)
  • Create Jira Ticket: creates a Jira issue and posts the ticket URL as a reply in the comment thread

The "Create Jira Ticket" button is only visible when Jira integration is configured.

How It Works

1. Review comment is posted

When Codity reviews a PR, it posts inline comments for each finding. Each comment contains the finding description, a code suggestion (where applicable), and the action buttons.

2. User clicks a button

Clicking Create Issue or Create Jira Ticket calls Codity's backend with the ID of that specific review comment. No additional input is required: the title and description are derived automatically from the finding.

3. Issue is created

For VCS issues (GitHub / GitLab / Bitbucket / Azure DevOps):

  • A new issue is opened in the same repository
  • The issue title and description are populated from the review finding
  • The issue URL is returned to the user

For Jira:

  • A new Jira issue of type Task is created in your configured Jira project
  • The description is formatted in Atlassian Document Format (ADF)
  • The finding details (file path, vulnerability type, description, code suggestion) are included

4. Reply is posted

After a Jira ticket is created, Codity automatically posts a reply in the PR comment thread with the Jira ticket URL, so the link between the PR finding and the ticket is visible to all reviewers.

Requirements

For native VCS issues

No additional configuration is required. Codity uses the existing installation credentials to create issues in the same repository.

For Jira issues

Jira integration must be configured in Settings. See JIRA Integration for setup steps.

The Jira project key used for issue creation is the first key listed in your Project Keys configuration.

Supported Platforms

PlatformNative Issue TypeJira Issue Creation
GitHubGitHub IssueSupported
GitLabGitLab IssueSupported
BitbucketBitbucket IssueSupported
Azure DevOpsWork ItemSupported

Next Steps