Skip to main content
Version: 2.0.0

Changelog

Release 1.0.0 · Forge 2.0.0​

First public release of Deepseek for Jira. The app joins Jira Cloud as an assignable companion and leaves the change in a draft pull request in Bitbucket.

New features​

  • Assignable companion: the agent appears in the Assignee field, in mentions, and in the Rovo Chat panel.
  • Immediate acknowledgement: the agent confirms the request before planning or touching code.
  • Work item reading: it reads the summary, description, comments, and text attachments. It skips binaries and says so.
  • Plan in the work item's language: it explains what it will do in the work item's language. In Spanish it uses spaces and work items.
  • Questions before implementation: if a critical decision is missing, it asks and waits for the answer in the chat.
  • Private Rovo Chat: the panel conversation is private and is not automatically copied to the work item.
  • Draft pull request: it works with a single Bitbucket repository, creates the deepseek/<key>-<slug> branch, and opens a draft pull request that cites the key.
  • Reviewable result: it returns the change summary, executed tests, risks, and the pull request link. The agent does not publish the comment on the work item.
  • Iteration: a later mention continues on the same branch and the same pull request.
  • Limits and cancellation: an in-progress task can be cancelled, and work stops when a token, step, or time limit is reached. Partial work is not published.
  • Site isolation: uninstalling deletes the site's credentials and tasks. A reinstall does not mix tasks from the previous cycle.

Scope of this version​

  • First installation on Jira Cloud. There is no upgrade path from a previous version.
  • The plan is generated from the work item text. In 1.0.0 the repository is not cloned for planning.
  • The agent does not write to the work item. A person publishes the comment.

Not included yet​

  • GitHub.
  • Jira Data Center.
  • An Atlassian Marketplace listing.
  • Billing.
  • Multiple repositories at once.
  • Multiple Bitbucket workspaces per site.
  • An administration page inside Jira.
  • A plan that clones the repository in read-only mode.