Skip to main content
Project Intelligence

Task editor

The task editor works with Jira, Bitrix24 (tasks), and Yandex Tracker. When the agent proposes to create a task, you have two ways to review its intent:

  • Fast path — right in the chat: a compact card with field diffs and "Accept / Reject" buttons.
  • Expanded path — the "Open in task editor" button: the same card becomes a prefilled task-creation form that you can correct before creating.

The expanded path is useful when the task is not trivial: you need to check the description, move it to another project, change the work type, assign someone, or adjust fields.

Supported systems​

SystemWhat it is
JiraProject work items: work types, estimates, versions, parent issues.
Bitrix24 (tasks)Portal tasks of Bitrix24: assignments and employee tasks.
Yandex TrackerTasks for IT and dev teams.

The creation mechanics are the same: an agent proposal, a prefilled form, a field check, then create or reject. The form's field set depends on the system and your project or portal configuration.

How it works​

  1. Proposal. The agent forms a create proposal (project, work type, summary, description, and other known fields).
  2. Opening the form. The "Open in task editor" button opens the working area with a form modeled after the familiar create dialog in your system:
    • project (space) and work type;
    • summary;
    • description in rich text;
    • assignee, parent issue, and additional fields — story points, dates, versions — depending on your project configuration;
    • required fields are marked: creation is blocked until they are filled.
  3. Editing. You change any displayed field. Your edits in the form become the actual content of the task: at creation time, exactly what you see is applied, not the original proposal snapshot.
  4. Create or reject. The Create button applies the change through the same verified channel as chat proposal application. The Reject button withdraws the proposal from review.
  5. Verification. After creation the system confirms the result: the task actually exists in the target system, and the card receives a link to it.

Good to know​

  • The form shows the fields the agent selected for the proposal and that your project's create screen supports. Create screens differ across systems and projects — the full field set is not guaranteed.
  • The agent never creates tasks without a person: creation is initiated only by the user, via the form button or "Accept" in chat.
  • Bulk creation of multiple tasks in one operation from the editor is not supported — each task is reviewed individually.
  • Detailed review of edits to an existing task (like the document review) is planned; at launch, the editor covers creation.

When to use it​

  • Decomposition: the agent proposes a set of subtasks — you review each one in the form.
  • Capturing agreements: after a discussion the agent proposes a task — you refine the wording and create it.
  • Planning corrections: moves and new stages are turned into tasks reviewed by a person.