Skip to main content
Version: Next

Installation Guide

Deepseek for Jira is installed as a Forge app on Jira Cloud. A Jira administrator or site administrator performs the installation.

Installation in version 1.1.0

This version is not published on the Atlassian Marketplace. Installation is performed with the Forge distribution link provided by MB Group. If you do not have the link, contact your Jira administrator or the MB Group team.

Prerequisites​

  • A Jira Cloud site.
  • Jira administrator or site administrator permissions to install apps.
  • A Bitbucket Cloud workspace available for the service. The OAuth consumer is configured during setup.
  • On development sites, the person using the agent must be an app contributor. If not, Jira shows a generic error.

Installation steps​

  1. Sign in to Jira Cloud with an administrator account.
  2. Open the Forge distribution link provided by MB Group.
  3. Select the Jira Cloud site if prompted.
  4. Review the requested permissions and confirm the installation.
  5. Wait for Atlassian to finish deploying the Forge app.
  6. Verify in Apps → Manage apps that Deepseek for Jira is installed.
  7. Check that the agent appears in the Assignee field, in mentions, and in the Rovo Chat panel.
Agent name

The agent's display name supports up to 30 characters.

Permissions and Bitbucket access​

The app requests these Jira scopes:

  • read:jira-work
  • write:jira-work (new in 1.1.0): post the reply to a mention as a comment on the work item.
  • read:app-user-token
  • read:app-system-token
  • Teamwork Graph read access (new in 1.1.0): read the work item's links, such as the repository, branch, commit, pull request, and linked pages. Reads are made on behalf of the person who assigned or mentioned the agent. The app does not write to the graph.
    • read:graph:issue:jira
    • read:graph:repository:external
    • read:graph:branch:external
    • read:graph:commit:external
    • read:graph:pull-request:external
    • read:graph:page:confluence
Teamwork Graph in preview

Reading links uses Atlassian's Teamwork Graph, which is in preview. If it does not respond, the agent continues with the other sources and says so in the panel.

The app does not request Bitbucket scopes. Bitbucket access uses a workspace OAuth consumer, never a personal API token. The consumer needs these scopes:

  • repository:write
  • pullrequest:write

The consumer and model provider are configured outside Jira during service setup. In 1.1.0 there is no administration page inside Jira. To change these values, contact the team that manages the service.

Upgrading from version 1.0.0​

Version 1.1.0 adds the write:jira-work scope and the Teamwork Graph read scopes (read:graph:*). Forge apps are updated through Atlassian's infrastructure, and when a version adds permissions, an administrator has to accept them.

  1. Go to Apps → Manage apps.
  2. Find Deepseek for Jira and accept the permissions update.

Until the update is accepted, the site stays on the previous version: the agent does not post the reply to a mention as a comment and does not read the work item's links.

After installation​

  1. Confirm that the agent appears in Assignee and in mentions.
  2. Open the Rovo Chat panel and check that it responds.
  3. Read the Administrator Guide to learn about the model, Bitbucket consumer, limits, the environment's network, and the data sent to the provider.
  4. Mention the agent on a test work item with a question and check that the reply is posted as a comment.

What happens on uninstall​

Uninstalling the app deletes the site's credentials and tasks. A reinstall creates a new registration and does not mix tasks from the previous cycle.

What the app writes to the work item​

The app only writes a comment when the agent is mentioned: it posts its final reply. An assignment does not post anything to the work item; the result stays in the agent's panel. Failures are not posted either: they stay in the panel.