Axial gaps
A gap is something Axial was asked to do and could not, because a tool, some data, a permission or a skill was missing. Logging gaps as they come up gives you a list of what to build or set up next, with a count of how often each one matters.
Gaps are logged from conversations with Axial’s agent, so they are offered where your installation has one. A gap is a request for work, not knowledge: Axial is never given the list of gaps to work from. For a fact Axial should use on other tickets, use a shared note instead.
Logging a gap
When you ask Axial to do something it cannot, in a ticket’s Axial panel or in an Axial conversation, ask it to log a gap, or agree when it offers. Axial records:
- What was asked and what was missing.
- The kind: tool, data, permission or skill.
- Whose it is: Our tools when one of your own tools, skills or actions lacks it, or Axial itself when Axial does.
Before a new gap is logged, the gaps still open are checked for one on the same subject, and Axial adds to that one if it is the same. A gap that keeps coming up gathers occurrences rather than copies, and its count shows how much it matters. Axial says in its answer which gap it logged.
Anyone with Work access to Axial can log a gap. Logged by someone without Manage access, a new gap is a recommendation for a manager to review, and what they add to an existing gap is recorded as theirs but changes nothing on it. A customer’s message can never log a gap, and one conversation logs at most five.
The Gaps page
Staff with Manage access to Axial open the list from their account menu: Axial → Gaps.
The list opens on the gaps Still to deal with (recommended, open or planned), with the most recent activity first. Use Status to see all gaps or those with one status, and Whose to see only Our tools or Axial itself.
Each gap shows its number, title, status, whose it is and its kind, how many times it has been seen and when last, and the ticket it first came up on. A gap raised by someone without Manage access is marked Recommended by with their name, and a count shows how many recommendations it has had from non-managers.
Click a gap to open it. It shows what was asked and what was missing, its status note, and its History: every time it was raised or seen, every recommendation and every change, with who, when and on which ticket.
Dealing with a gap
With a gap opened, you can change:
- Status: Open, Planned, Done or Won’t do. A gap logged by a non-manager starts as Recommended until you give it one of these.
- Whose, Kind and Title, to correct what Axial recorded.
- Status note: why it has this status, what was done or why not.
Click Save. Each change is added to the gap’s history with your name.
When two gaps are the same, enter the number of the one to keep under Merge into gap # and click Merge. The merged gap keeps its history and points to the other, and a conversation that names it later is taken to the one you kept.
Gaps can also be listed and updated through the MCP server’s Axial tools.