Industries / Software

Work tracking for software teams

Features, bugs and releases move from the backlog through review to release on one board. Cycles open on their own and points add up, so you see what will make it and what will not before the cycle ends.

The problem

Nobody knows what will make it by the end of the cycle

Customer requests, bugs and planned work get mixed up in one list. How much work went into the cycle, how much is done and what is waiting in review only becomes clear on the last day.

  • An urgent bug jumps the queue and the cycle's scope changes without anyone being asked.
  • Work waiting in review is taken for done.
  • Which code belongs to which item is searched for in commit messages.

How Neoli solves it

One board from backlog to release

Backlog, To do, In progress, In review and Done come set up. Cards show the estimate, priority and labels; drag a card to change its state, or split the board into swimlanes by owner or label.

A software project's board: Backlog, To do, In progress, In review and Done

What is in this cycle, and what is left

Two-week cycles open on their own. Group this cycle's work by state: each group shows its points and how many items are closed, so work waiting for review is not taken for done. Unfinished work moves to the next cycle.

This cycle's work grouped by state, with closed counts and point totals

All of a feature's context

A feature's sub-items, point estimate, cycle and linked support tickets on one screen. With GitHub or Gitea connected, branches, commits and pull requests that mention its code are linked too, and a merge moves the item forward.

A feature item: sub-items, linked support tickets, point estimate and cycle

What comes set up

States

  1. Backlog
  2. To do
  3. In progress
  4. In review
  5. Done

Item types

  • Task
  • Bug
  • Feature
  • Milestone

Also ready

  • Bug report, feature and release templates with their sub-items
  • Incident template: impact, workaround, root cause, permanent fix, post-incident review
  • Story points, two-week cycles that open on their own
  • Ready views: by phase, my open work, due this week, overdue, board by owner

Where do these setups come from?

Each setup is a starting point drawn from how that kind of work commonly runs: the state names, item types and steps come from the words those teams use. It does not know your process, so everything in it is yours to change. Tell us what is missing at destek@neoli.app and we improve the setups.

Frequently asked questions

How does it connect to GitHub or Gitea?

You set up the connection in the workspace settings; branches, commits and pull requests that mention an item's code are linked to it, and the rules you choose move the item forward on merge.

How do cycles work?

In the software setup two-week cycles open on their own. You take items into a cycle; unfinished ones move to the next when it closes, and the cycle report shows what was taken and what was done.

How do I handle an incident?

The incident template opens impact assessment, workaround, root cause, permanent fix and post-incident review as steps; you write the timeline in the description and link the related bugs and tickets.

Other industries

Your kind of work is not listed?

Start with the General setup: it comes with phases, tasks and milestones; you add your own states, item types and fields. When it fits, keep the project as a template.

Start with the General setup

Bring your team's plan into one place

Open your workspace in a minute and invite your team.

Start free