Docs › Services/Project › Agile All in One with AI Subtasks

Agile All in One with AI Subtasks
Break a story into subtasks with points: the model AI Assistant is set up with proposes them, you tick and edit, and the ones you keep are created under the story.
bambooforge_agile_aiKey facts
- Not for
- Send less than the whole description. The title, the whole description as text and the story points go to the model; nothing is cut or masked.; Count a story once. The subtasks carry points of their own in the story's sprint, and Agile adds them to the story's: the sprint's committed points, the velocity and the epic's progress count both.; Limit who asks or how often. Every project user may ask, as often as they press.; Run without AI Assistant set up. It needs a key or a local server there.
- Manual last updated
- 2026-11-12
Break a story into subtasks: the model AI Assistant is set up with reads the story and proposes subtasks with story points; you untick, edit, and the ones you keep are created under the story, in its sprint and epic. It installs by itself where Agile Sprints & Board and AI Assistant are both installed. For Odoo 20, Community or Enterprise.
This page is the complete manual: what is sent to the model, who may send it, what is created, and what the helper does not do.
Overview
For whom. A team on Agile Sprints & Board for Projects that writes its stories in Odoo and wants a first cut of the subtasks to work from. It adds one button to the task form and a dialog; it changes nothing of Agile's screens or figures.
What it does
A proposal on demand. Break into subtasks with AI on a task opens a dialog; Propose with AI asks the model AI Assistant is set up with for three to eight subtasks with story points.
A list to tick. Every proposed subtask is a line you untick or edit, name and points, before anything is created; Propose again asks again and replaces the list.
Subtasks under the story. Create the ticked ones creates them as tasks of type Task under the story, in its project, sprint, epic and stage, and notes in the story's chatter how many were created.
A plain answer read too. When the model answers with lines instead of the list it was asked for, each line becomes a subtask to tick, without points.
Off when AI Assistant is off. With AI assistant enabled unticked for the story's company, nothing is sent.
What it does not do
Send less than the whole description. The title, the whole description as text and the story points go to the model; nothing is cut or masked.
Count a story once. The subtasks carry points of their own in the story's sprint, and Agile adds them to the story's: the sprint's committed points, the velocity and the epic's progress count both.
Limit who asks or how often. Every project user may ask, as often as they press.
Run without AI Assistant set up. It needs a key or a local server there.
What it needs
Odoo 20, Community or Enterprise, with Agile Sprints & Board for Projects and AI Assistant installed; this helper then installs by itself.
AI Assistant set up with a server: OpenAI with an API key, or a local server (Ollama or another one with the OpenAI chat API).
Project users to break stories down.
Concepts
Story. A task the team will break down; its title and description are what the model reads.
Proposal. The list of subtasks the model answers with, to tick and edit before anything exists.
Subtask. A task under the story, in its sprint and epic, with points of its own.
AI Assistant. The app that keeps the model's server and key; this helper asks through it.
Install and first run
Install Agile Sprints & Board for Projects and AI Assistant.
Expected: Agile All in One with AI Subtasks installs by itself.
In Settings, AI Assistant's block: choose OpenAI and paste a key, or choose a local server and give its address and model; press Test the connection.
Expected: the test answers.
Open a task, page Agile, and press Break into subtasks with AI.
Expected: a dialog that says the model reads the story and proposes subtasks with points.
Press Propose with AI.
Expected: three to eight lines, each ticked, with a name and points.
Uninstalling
Uninstalling removes the button and the dialog. The subtasks it created stay, as ordinary tasks under their story.
Flows
One thing to do with the helper.
Break a story into subtasks
Write the story's title and description, and its story points if you have them.
Press Break into subtasks with AI, then Propose with AI.
Untick the lines you do not want, and correct names and points in the list.
Propose again to ask the model again: the list is replaced.
Create the ticked ones: the subtasks are created under the story and the dialog closes.
How it works
What leaves the database
To the model: an instruction to answer with a list of three to eight subtasks with points in the Fibonacci scale, then the story's title, its whole description as plain text, and its story points when it has some. Nothing else of the task: no chatter, no attachments, no assignee, no customer.
To which server: the one AI Assistant is set up with. OpenAI receives it with the API key AI Assistant keeps; OpenAI's retention of the conversation is off unless AI Assistant's retention setting is on. A local server receives it at its own address and nothing leaves your network.
When: only when Propose with AI or Propose again is pressed.
What the answer becomes
An answer holding a list of entries with a name and points gives one line per entry.
Any other answer gives one line per line of text, its numbering or bullet removed, cut at 120 characters, with 0 points.
An empty answer is refused with a message; a server that does not answer gives its error.
Create the ticked ones creates each ticked line as a task: the line's name and points, type Task, the story as parent, and the story's project, sprint, epic and stage. A story in a folded stage gives subtasks that are already done.
Who may use it, and who pays
Every project user may open the dialog, ask the model and create the subtasks, on the stories they may read; the subtasks are created with their own rights.
The cost of each question goes to the account of the key AI Assistant keeps: one key for the database, whoever asks. Nothing counts or caps the questions.
A company whose AI assistant enabled is unticked sends nothing: the story's company, or the user's when the story has none.
What leans on Odoo's settings
AI Assistant's server (OpenAI by default): OpenAI needs an API key; a local server needs its address and model.
AI assistant enabled (per company, on by default): off, this helper sends nothing for that company.
OpenAI retention (off by default): whether OpenAI keeps the conversations for its own tools.
Developer mode: not needed: the button is on the task's Agile page.
How we make sure it works
Before every release, 4 automated checks run against this app on Odoo 16, 17, 18, 19 and 20. Among them:
A silent model is an error not a blank list.
Proposals are parsed ticked and created under the story.
The complete list is in the source you receive.
For managers
The helper has no analysis of its own: the subtasks it creates count in Agile's velocity, burndown and epic progress, under Project > Agile > Agile Reports and on each sprint.
Troubleshooting and FAQ
AI Assistant is not configured yet: add a key or a local server in Settings. OpenAI is chosen and no key is set: paste one, or choose a local server.
AI Assistant is switched off for ..., so the story is not sent. An administrator ticks AI assistant enabled in Settings for that company.
The model did not answer: ... The server refused or did not answer; the message says why (a wrong key, a local server not running).
The model answered with nothing usable. Try again, or write the subtasks by hand. The answer was empty.
Questions people ask
- Is anything created without me pressing Create?
No. The proposal is a list in the dialog until Create the ticked ones.
- Can the model see our other tasks or customers?
No. It receives the story's title, description and points, and the instruction.
- Can I keep everything on our own network?
Yes: set AI Assistant to a local server, and the story goes to it only.
- Does it estimate the story itself?
No. It proposes points for each subtask; the story keeps its own.
Support
Write to support@bambooforge.dev with your Odoo series, the AI server you use and what the screen said.
Changelog
20.0.1.0.1
Help texts on every field of the dialog.
A manual of its own: what is sent to the model and to whom, who pays, what the answer becomes, and what the helper does not do.
20.0.1.0.0
Built for Odoo 20: access rights on Odoo 20's single access model.
Break this into subtasks: the model AI Assistant is pointed at reads the story and proposes the subtasks with points; you tick, edit, and they are created under the story. Installed by itself alongside Agile Sprints & Board and AI Assistant.
Reference
Generated from the module's own code (version 20.0.1.0.1, series 20.0) on 2026-11-12; every menu, field, setting, scheduled action, group, rule, report and endpoint below is read from the files, not written by hand.
Models
bf.agile.subtasks (wizard)
Break a story into subtasks
Field |
Technical name |
Type |
Help |
Flags |
|---|---|---|---|---|
Task |
task_id |
Many2one to project.task |
The story to break down. Its title, its description and its story points are sent to the model. |
required |
Line |
line_ids |
One2many to bf.agile.subtasks.line |
The subtasks the model proposed. Untick or edit them before you create them. |
|
Ai Available |
ai_available |
Boolean |
Whether AI Assistant has a model to ask: a local server, or OpenAI with an API key. |
computed |
bf.agile.subtasks.line (wizard)
Proposed subtask
Field |
Technical name |
Type |
Help |
Flags |
|---|---|---|---|---|
Wizard |
wizard_id |
Many2one to bf.agile.subtasks |
The proposal this line belongs to. |
required |
Select |
select |
Boolean |
Ticked lines become subtasks when you press Create the ticked ones. |
|
Name |
name |
Char |
required |
|
Points |
points |
Float |
The model's estimate in story points. Change it before you create the subtasks. |
project.task (extends Odoo's project.task)
Adds no fields.
Security
Access rules
Model |
Group |
Read |
Write |
Create |
Delete |
|---|---|---|---|---|---|
bf.agile.subtasks |
project.group_project_user |
yes |
yes |
yes |
yes |
bf.agile.subtasks.line |
project.group_project_user |
yes |
yes |
yes |
yes |
Server actions and wizards
Wizards (transient models, described above):
bf.agile.subtasks: Break a story into subtasks
bf.agile.subtasks.line: Proposed subtask