Issues and workflow

• Issue types. Epic, Story, Task, Bug and Sub-task. An issue's type and project never change after creation.

• Keys and references. Every issue has a readable key per project, such as ABC-00042. Anywhere an issue is referenced, its key, its id or its in-app link all work.

• Statuses. Backlog, To do, In progress, Testing, In review, Done and Reopened. Each organization can rename them to its own words.

• Configurable workflow. Which status may follow which, and on what condition, is a workflow drawn in a graphical editor. It is set for the whole organization and can be refined per division, team or project. Available conditions include:

  • required sections filled in;
  • no open blockers;
  • a role or the assignee;
  • a current, verified plan;
  • a Definition of Done satisfied;
  • time logged;
  • the code having reached a given branch or version line.

  A refused move says which condition failed and why.

• Closing work. Every Done carries a resolution: Fixed, Won't fix, Duplicate, Cannot reproduce or Incomplete. Work closed as not delivered can go to Done from any status.

• Sizing and dates. Severity, story points, time estimates, planned start and due dates.

• What an issue produces. Delivery, investigation, technical or management work. Velocity counts delivery, and the rest is reported beside it.

• Typed sections. Sections such as pre-analysis, decisions, verification and resolution, configurable per project.

  • A pre-analysis can list the files it examined with their checksums.
  • It goes stale when those files change, so a plan made on old code is visible as such.

• Definition of Done. Checklists defined at organization, division, team or project level, copied onto each issue.

• Relations. Relates to, caused by, duplicates and blocks.

• Discussion and files.

  • Comments on the description or on a single section.
  • Attachments, downloadable once the antivirus allows.

• For the client. A client-facing summary per issue, kept apart from the internal text.

• History and trash.

  • Every change is in the issue's history.
  • Deleted issues go to the project's trash and can be restored.

• Ordering and views. Manual ordering by drag and drop, a "My issues" view, and a home page that adapts to newcomers and to experienced users.