Creating Issues | Elixion Docs

Elixion, the platform for Engineering Intelligence™, keeps issue creation to one form. This page covers where that form opens from, what each field does, and the two shortcuts that fill it in for you: a template, and an AI draft.

Opening the form

| Route | How | |-------|-----| | Keyboard | Press c anywhere in the app | | List | The New issue button at the top of the issue list | | Project overview | The new issue action on a project's page | | Epic | The create action on an epic, which pins the new issue to that epic | | Board | The + on a column header |

The board's + is deliberately smaller than the rest: it opens an inline composer that takes a title and nothing else, and creates a Task at Medium priority in that column's status. Everything else opens the full form.

You can also generate issues from a prompt. Press Cmd+J or Ctrl+J, type /story, /task, /bug or /epic and describe the work. Nothing is written until you review what came back and confirm it. See Prompting Panel.

The form

Fields appear in this order.

Start from template. A picker of the templates available in this project, plus your own personal ones and any global ones. It reads "None, start from scratch" until you choose. A template can prefill the title, description, type, priority, labels, story points, acceptance criteria, definition of done, components, epic and assignee, and can require you to fill named fields before you submit. If the project has no templates yet the picker is replaced by a line saying so. A Manage templates link beside the label opens the templates page in a new tab, so nothing you have typed is lost. See Issue Templates.

Title. A short, action oriented summary. Required.

Description. A rich text editor: formatting, links, images and file attachments from the toolbar.

Acceptance criteria. Its own field, not a heading inside the description. Write measurable outcomes here, and both the reviewer and any agent working the issue read them from the same place.

Story points. The input follows the estimation scale the project is configured for, so what you see may be a Fibonacci picker, a t shirt size or a plain number.

Estimate (hours). Original estimate in hours.

Type. Task, Story, Bug, Epic, Spike or Tech Debt. Task is the default.

Priority. Critical, High, Medium, Low or Trivial. Medium is the default.

Labels. Type a label and press Enter. Labels are lower cased so Bug and bug do not end up as two labels.

Epic. Optional. Locked when you started the form from an epic.

Assignee. Optional, and this is the field worth pausing on. The list has two groups: Users and AI Agents. Picking an agent assigns the work to that agent rather than to a person, and depending on the agent's autonomy level the run can start from the assignment. Agent options are disabled, and marked "(connect a repo)", until the project has a repository connected. See GitHub and Using Agents.

Sprint. Only appears for projects that run sprints. It offers the project's active, draft and planned sprints, active first.

There is no status field on the create form. A new issue starts in Backlog, except from the board's inline composer, which creates it in the column you added it to.

Drafting with AI

The Suggest with AI button in the footer takes the title you have typed, and the description if there is one, and comes back with a draft: a sharper title, a description and acceptance criteria. You see it as a proposal under the heading "Review AI draft", and you either apply it to the form or discard it. Nothing is created until you press Create issue. The button needs a title of at least five characters.

Attachments

Files go on the description through the editor toolbar, and on an issue afterwards through its Attachments section.

Up to 50 MB per file.
Images: JPEG, PNG, GIF and WebP. SVG is rejected, because an SVG can carry a script and would run when someone opens the stored file.
Documents: PDF, Word, Excel, PowerPoint, plain text, CSV and Markdown.
Data and archives: JSON, XML, ZIP and GZIP.
Executable and script extensions are rejected whatever their declared type.

After it is created

The issue opens on its own page. From there you can:

Set a due date, remaining estimate or time spent.
Add components and an environment note.
Link it to other issues with Blocks, Blocked by, Relates to and the rest. See Dependencies.
Assign it to an agent if you did not at creation time.
Break it into subtasks.

Writing an issue an agent can act on

An agent reads the same words you do, and nothing else.

Put the outcome in the title. "Card totals ignore refunds" beats "Fix billing".
Fill in acceptance criteria. This is the field that decides whether the work comes back finished or approximately finished.
Name the files, endpoints or screens involved in the description.
Connect the repository first. Without one, agent options on the assignee list stay disabled.