What is planned
Where Andare stands today, the work that is scheduled next, and the things it is deliberately not going to do.
Where it stands
Boards, sprints, issues, the query language and automation are in use — this site’s own work is tracked in Andare.
Current work is about the tracker knowing what the code is doing, and about agents that can carry a goal rather than a single ticket.
Planned work
What is being built
Grouped by theme and ordered by intent. These are horizons, not dates — nothing on this page is a delivery commitment, and the order can change when a customer gives us a reason to change it.
-
In progress
The tracker and the code, aware of each other
Today an issue and the branch that closes it are related only by a human remembering to say so. This group closes that gap in both directions: the code tells the tracker what happened, and the issue shows it.
- A development panel on the issue, showing its branches and pull requests
- Issue keys read out of branch names and commit messages
- A signed GitHub webhook receiver
- Automation triggers when a pull request opens or merges
- Issue status that moves when its pull request merges
-
In progress
Goal-directed agent work
Andare can already hand a single well-specified ticket to a coding agent. The next step is longer-lived: one open goal per project that an agent plans, works in cycles, and closes over time — with every cycle recorded as work you can read.
- One open goal per project, with its own schema, rules and permissions
- Create, update, pause and close a goal
- Each cycle recorded as a task, linked to the issues it touched
- Tracker tools exposed over MCP so an agent can list, read and record against a goal
- A web view showing what each cycle actually did
-
Next
Keeping a board legible as it ages
A tracker that never forgets anything becomes unreadable. This group is about what happens to work after it is finished, and about the board itself being pleasant to use at real column counts.
- Archiving issues done for longer than a chosen period
- A scheduled job applying the archive rule
- Per-organisation email templating
- Board layout fixes for empty and uneven columns
Out of scope
Not on the roadmap
Said plainly, because the alternative is a sales conversation that ends in disappointment. If one of these is the thing you need, Andare is not the product for it.
-
Being a Jira migration tool
Andare reads its own data. Importing another tracker’s history faithfully is a product in itself.
-
Time tracking and billing
Hours belong next to the ledger, not the board.
How this is maintained
Every item above corresponds to work tracked in our own issue tracker, and this page is rewritten from that tracker rather than kept by hand. What is not shown: unfixed defects and security work, which belong in the tracker until they are closed, not on a product page.
Want the detail behind a line on this page, or a view of where something sits? Write to dmoore@dwmmholdings.com and ask.
Next
Bring Andare into your company
Ask about onboarding an organisation, migrating existing records, or a demonstration.