Frequently asked questions
General usageβ
What is the difference between assigning, mentioning, and using Rovo Chat?β
Assigning or mentioning works on the work item. Rovo Chat is a private conversation for instructions or feedback without a new assignment. The Rovo Chat conversation is not automatically copied to the work item. See Plan and questions.
What does the agent read?β
The work item summary, description, comments, and text attachments. Binary attachments are skipped and the agent says so.
What language does it respond in?β
The work item's language. In Spanish it uses Jira's current terminology: spaces and work items.
Does the agent write to the work item?β
No. The agent does not publish comments on the work item. The result stays in the agent response and Jira offers to draft the comment. The reviewer decides whether to publish it.
Planning and questionsβ
Does the plan clone the repository?β
No. In version 1.0.0, the plan is generated only from the work item text. The repository is used when implementation starts.
What happens if a decision is missing?β
The agent asks and waits for the answer in the chat. Questions are asked only during planning. During implementation there are no questions or permission prompts.
What happens if the site does not have the model or Bitbucket access configured?β
The agent asks an administrator to complete the configuration and does not promise the change. Configuration is performed outside Jira during service setup. See the Administrator Guide.
What data is sent to the model provider?β
The work item text, comments, and text attachments. When it implements, it also sends the relevant diff. No secrets or Jira token are sent. See the Administrator Guide.
Pull request, iteration, and limitsβ
Which repositories does it support?β
A single Bitbucket repository from the configured workspace. If there is no repository or there are several, the agent asks. GitHub URLs are ignored. It does not support multi-repo or multiple Bitbucket workspaces per site.
What is the branch name and how is the pull request created?β
The branch is named deepseek/<key>-<slug>. The pull request is created as a draft and cites the work item key. See Draft pull request.
Does the agent push to the default branch or merge?β
No. The agent does not push to the default branch or merge.
What happens if implementation fails?β
The message explains why. There is no push to the default branch. If information is missing, the task ends with a suggested question and you can continue with a mention.
How do I iterate on the same pull request?β
Mention the agent with the new instruction. It continues on the same branch and the same pull request, with new commits on that branch. It does not open another pull request or merge.
Can I cancel a task?β
Yes. You can cancel an in-progress task, including during implementation. The work stops and partial work is not published.
What usage limits are there?β
Token, step, and time limits per task. When a limit is reached, the task stops, the message states which limit was reached and what was completed, and partial work is not published. See Draft pull request and the Administrator Guide.
Installation, version, and scopeβ
How is the app installed?β
A Jira administrator opens the Forge distribution link provided by MB Group and confirms the permissions. On development sites, the person using the agent must be an app contributor. See the Installation Guide.
What happens on uninstall?β
The site's credentials and tasks are deleted. A reinstall creates a new registration and does not mix tasks from the previous cycle.
Is there an administration page inside Jira?β
No. The model, Bitbucket OAuth consumer, and usage limits are configured outside Jira during service setup. To change them, contact the team that manages the service.
Is it available on the Atlassian Marketplace?β
Not in version 1.0.0. Installation uses the Forge distribution link provided by MB Group.
What does version 1.0.0 not include?β
GitHub, Jira Data Center, a Marketplace listing, billing, multi-repo, multiple Bitbucket workspaces per site, an administration page inside Jira, and a plan that clones the repository.