Installation Guide
Deepseek for Jira is installed as a Forge app on Jira Cloud. A Jira administrator or site administrator performs the installation.
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​
- Sign in to Jira Cloud with an administrator account.
- Open the Forge distribution link provided by MB Group.
- Select the Jira Cloud site if prompted.
- Review the requested permissions and confirm the installation.
- Wait for Atlassian to finish deploying the Forge app.
- Verify in Apps → Manage apps that Deepseek for Jira is installed.
- Check that the agent appears in the Assignee field, in mentions, and in the Rovo Chat panel.
The agent's display name supports up to 30 characters.
Permissions and Bitbucket access​
The app requests these Jira scopes:
read:jira-workread:app-user-tokenread:app-system-token
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:writepullrequest:write
The consumer and model provider are configured outside Jira during service setup. In 1.0.0 there is no administration page inside Jira. To change these values, contact the team that manages the service.
After installation​
- Confirm that the agent appears in Assignee and in mentions.
- Open the Rovo Chat panel and check that it responds.
- Read the Administrator Guide to learn about the model, Bitbucket consumer, limits, and the data sent to the provider.
- Assign a test work item and review the plan the agent returns.
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.
The app does not write to the work item​
The agent does not publish comments on the work item. The change summary stays in the conversation and Jira offers to draft the comment. The reviewer decides whether to publish it.