Skip to main content
Version: 3.0.0

Introduction to Deepseek for Jira

Deepseek for Jira is a Forge app for Jira Cloud that works as an assignable companion. Assign it a work item or mention it, and it leaves the change in a draft pull request in Bitbucket for review before merging. It also answers questions, looks up the code cited in the work item, and reviews pull requests that are already open.

Deepseek agent in the Assignee field

Who is it for?​

It is designed for teams that want to delegate small or well-scoped code changes and review them like any other pull request, and for anyone who needs a quick answer about the code or a second opinion on a pull request. When mentioned, the agent replies with a comment on the work item. When assigned, the result stays in its panel.

What's new in version 1.1.0​

CapabilityBenefit
Reply as a commentWhen mentioned, the reply is posted as an agent comment on the work item, with tables, code, and lists. When assigned, the result stays in its panel.
Questions without codeIf the mention does not ask for a change, it answers directly without touching the repository.
Questions about the codeIf the work item cites a repository, branch, or pull request, it reads it in read-only mode and answers. It does not commit or push.
Review of an open pull requestEvaluates a pull request without modifying it and returns a verdict stating what is wrong and in which file.
Plan with the repository in viewReads the repository structure before proposing the change, without modifying it.
More checks before publishingExplores the code before editing and runs tests, forge lint, and a Forge review, with a security review when the change is sensitive.
Official Forge documentationLooks up the current Forge documentation and follows Atlassian's official practices while it works.
Work item linksReads the linked repository, branch, pull request, and pages to know what to work on.
Progress in the panelTask progress is visible in the panel while the agent works.

Capabilities available since version 1.0.0​

CapabilityBenefit
Assignable companionAppears in the Assignee field, in mentions, and in the Rovo Chat panel.
Immediate acknowledgementConfirms the request right away; the long-running work continues afterwards.
Work item readingReads the summary, description, comments, and text attachments. It skips binaries and says so.
Plan in the work item's languageExplains what it will do in the work item's language.
Questions before implementationIf a critical decision is missing, it asks and waits for the answer in the chat.
Private Rovo ChatThe panel conversation is private and is not automatically copied to the work item.
Draft pull requestWorks with a single Bitbucket repository and opens a draft pull request.
Reviewable resultReturns the change summary, executed tests, risks, and the pull request link.
IterationA later mention continues on the same branch and the same pull request.
Limits and cancellationAn in-progress task can be cancelled, and work stops when a usage limit is reached.
Site isolationEach installation is registered and separated. Uninstalling deletes the site's credentials and tasks.

How it works​

  1. Assign the work item to the agent, mention it in a comment, or talk to it in Rovo Chat.
  2. The agent confirms the request and reads the available context, including the work item's links.
  3. If the request is a question, it answers. If it is about the code or an open pull request, it reads it without modifying it and answers.
  4. If the request is a change, it explains a plan with the repository in view. If a decision is missing, it asks and waits.
  5. It applies the change in an isolated environment and validates it with tests, forge lint, and a review before publishing it.
  6. It opens a draft pull request in Bitbucket and returns the summary, tests, risks, and link. If you mentioned it, the reply is posted as a comment on the work item.
  7. You review the pull request. If you want changes, mention the agent again and it continues on the same pull request.

What version 1.1.0 does not include​

  • GitHub.
  • Jira Data Center.
  • An Atlassian Marketplace listing.
  • Billing.
  • Multiple repositories at once.
  • Multiple Bitbucket workspaces per site.
  • An administration page inside Jira.

The model, Bitbucket OAuth consumer, and usage limits are configured outside Jira during service setup. In 1.1.0 there is no administration page inside Jira.

Version​

This documentation describes version 1.1.0 of the product. The installed Forge version is available in Apps → Manage apps.

Next step: Installation Guide.