Skip to content

Issue types

Use this reference when you want to understand how Aisman classifies issues and links between them.

IDTypeWhen to use
1New featureA brand-new capability.
2ImprovementA visible enhancement to an existing feature.
3DocumentationHelp or documentation updates.
4TaskInternal work that does not change user-visible behavior.
5Change requestA requested change to existing behavior or presentation.
6BugA defect or regression.
7DuplicateA duplicate of another issue.
IDStatusMeaning
1Not implementedNo confirmed implementation recorded yet.
2Implemented by AIImplemented by the AI agent and awaiting user verification/follow-up.
3Partially implementedWork started but not complete.
4Has errorsImplemented with known problems.
5ImplementedConfirmed complete implementation.
6CancelledNo longer planned for implementation.
7RemovedRemoved after being introduced.
8TransitionedMoved/transitioned in workflow context.

In issue detail, description, outcomes, and notes can be presented in a combined workflow-oriented view.

  • Notes are typically shown newest-first by default.
  • You can switch note ordering when needed.
  • Status actions (for example Partial, Errors, Done, Canceled) are tied to implementation tracking.

For brand-new issues that do not yet have implementation-result notes, Aisman can expose a direct mark-as-implemented path so you can add the first implementation note quickly.

Besides AI-produced result notes, you can add your own manual notes during testing and validation.

  • Use manual notes to capture what you verified or corrected.
  • Keep notes short and outcome-focused so later triage is faster.
IDRelationshipInverse relationship
1relates torelated from
2depends onis dependency of
3extendsis extended by
4documentsis documented by
5fixesis fixed by
6duplicatesis duplicated by

When you review related issues, use these labels to understand why one issue is connected to another.