Skip to main content
Version: Next

Changelog

Release 1.1.0 · Forge 3.0.0​

Minor release on top of 1.0.0 (Forge 2.0.0). The agent goes from only implementing to also answering, looking up code, and reviewing pull requests on the work item. The changes it publishes go through more checks before the push.

New features​

  • Reply as a comment: when the agent is mentioned, its final reply is posted as a comment on the work item, replying to the comment that mentioned it. When assigned, the result stays in its panel.
  • Questions without code: if the mention does not ask for a change, the agent answers directly without opening the repository.
  • Questions about the code: if the work item cites a repository, branch, or pull request, the agent reads it in read-only mode and answers. It does not commit or push.
  • Review of an open pull request: the agent evaluates a pull request without modifying it. It runs the tests and, for a Forge app, forge lint, and gives a verdict stating what is wrong and in which file.
  • Plan with the repository in view: before proposing the change, it reads the repository's manifest, package.json files, AGENTS.md, and entry points, without modifying them.
  • Work item links: it reads the repository, branch, pull request, and linked pages (title and URL only) from the Teamwork Graph. Atlassian feature in preview: if it does not respond, the agent continues with the other sources and says so.
  • Official Forge documentation: the agent looks up the current documentation on developer.atlassian.com and follows Atlassian's official guides for Forge apps.
  • Progress in the panel: task progress is visible in the panel while the agent works.

Behavior changes​

  • More checks before the push: the agent explores the code before editing and, after the tests, runs forge lint and a Forge review. If the change touches permissions, network, authentication, or storage, it adds a security review. If forge lint fails, there is no push. If the review finds blockers, it fixes them once; if they remain, it does not publish.
  • Environment network: the agent's environment only reaches two destinations: the model endpoint and developer.atlassian.com. Any other destination is blocked.
  • Step limit: the default goes up from 40 to 80 steps per task.

Fixes​

  • Pull request by repository: if the work item only cites the repository, the agent looks there for the pull request for the key. It also accepts the Bitbucket URL that Jira copies from the Development panel.
  • Comment formatting: the agent's comment keeps tables, code, and lists instead of showing raw Markdown.

Upgrade notes​

  • New permissions: write:jira-work, to post the comment, and the Teamwork Graph read scopes (read:graph:issue:jira, read:graph:repository:external, read:graph:branch:external, read:graph:commit:external, read:graph:pull-request:external, and read:graph:page:confluence), for the work item's links.
  • An administrator has to accept the new permissions in Apps → Manage apps. Until then, the agent does not comment or read the work item's links.
  • An assignment still does not post to the work item. Failures stay in the panel.

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.

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.