Skip to main content
Version: 2.0.0

Plan and questions

When you assign a work item to the agent, mention it in a comment, or talk to it in Rovo Chat, the agent starts by understanding the request and explaining what it will do.

How to start work​

MethodWhat it does
AssignThe agent appears in the Assignee field and works on that work item.
MentionThe agent receives the instruction in a comment and responds in the same context.
Rovo ChatOpens a private conversation to give instructions or feedback without a new assignment.

The Rovo Chat conversation is private to the person writing. It is not automatically copied to the work item and does not open another active task.

Rovo Chat panel with the Deepseek agent

Acknowledgement​

The first thing the agent returns is an acknowledgement. The long-running work does not happen inside that first response.

What the agent reads​

It readsIt does not read
The work item summary and description.Binary attachments.
The work item comments.Secrets or credentials.
Text attachments.The Jira token.

When implementation starts, it also uses the relevant repository context. If there are binary attachments, the agent skips them and says so in the conversation.

Plan language​

The agent explains the plan in the work item's language. In Spanish it uses Jira's current terminology: spaces and work items.

Agent plan in the work item's language

Questions​

If a critical decision is missing, the agent asks and waits for the answer in the chat. It does not continue until it has one.

  • Questions are asked only during planning.
  • During implementation there are no questions or permission prompts.
  • If the site does not have the model or Bitbucket access configured, the agent asks an administrator to complete the configuration.
  • If implementation is blocked by missing information, the task ends with the reason and a suggested question. You can continue with a mention.

Agent question when a critical decision is missing

The plan does not clone the repository​

In version 1.0.0, the plan is generated from the work item text. The agent does not clone the repository to plan. The repository is used when implementation starts.

Data sent to the provider​

The agent sends the work item text, comments, and text attachments to the model provider. When it implements, it also sends the relevant diff. It does not send secrets or the Jira token. See the Administrator Guide for details.

Next step: Draft pull request.