aiku
Documentation

Projects in tickets

4 min read · #tickets · #projects · #help desk

Finding projects

In the left menu open Tickets, then Projects in the top menu. Every project is a card showing its health, status, progress bar, owner and team. Click one to open it.

Starting a project

Press New project and fill in Name, Goal (what done looks like), Start, Target (the date you want it finished), Owner and Team. Press Create. Anyone can start a project.

The project page

At the top a strip shows the Health (the mark from the latest update that has one), the Status, the Owner and team, the progress bars, and the counts Open, Done and Days left. The buttons New ticket and New task create work that is already in the project. Edit changes the project details (only for people who can change the project, see below).

The page has five tabs: Overview, Work, Timeline, Commits and Activity.

Putting work in

Tickets and tasks count together. On the Work tab:

  • Paste references: in the box type the references, for example HELP-123, TASK-45 - several at once, tickets and tasks mixed, is fine. Optionally pick a milestone, then press Add.
  • New ticket or New task: at the top of the page.
  • From a ticket or task: the side panel has a Project chip and a milestone chip. Click to pick a project or milestone, or choose No project or No milestone to clear it.

To take an item out from the project page, click the x next to it.

Work tab

Search, and filter by Tickets and tasks, milestone, person (Everyone or Unassigned), and tick Show closed to include finished work. Switch between List and Board (columns Todo, In progress, Done, and Cancelled when closed work is shown). In the list, work is grouped by milestone and each row has its own milestone selector.

Work you are not allowed to see is not listed; the page says how many confidential items are hidden.

Overview tab

  • Goal of the project.
  • Progress updates: write what moved, what is blocked and what comes next, optionally mark On track, At risk or Off track, then press Post update. Updates stay in order, newest first. The owner and the rest of the team are told straight away, in the Aiku bell and by email; the person who posted is not.
  • Milestones: a checklist with start and due dates and a small progress bar per milestone (items done out of items). Tick one to finish it; rename, reorder or remove with the small controls. Past its due date and not ticked it is marked Overdue.
  • Workload: per person, how many items are todo, in progress and done.

Timeline, Commits and Activity

  • Timeline: the milestones along a calendar with a Today line, and a Burn-up chart comparing all the work (Scope) with what is Done week by week and an Ideal line.
  • Commits: the code changes that fixed the project's tickets, with Version, Deployed, Commit, Subject and the Ticket. They appear by themselves when a ticket's fix is deployed.
  • Activity: what happened, newest first: work added or finished, updates, deployments. It is built automatically.

Reading progress

The progress bars show how much of the work is done and how far we are between start and target. The work bar turns red when it is more than 10 points behind the time. Past the target date it counts the days over. Cancelled work is left out of the totals.

Through the AI assistant

You can also ask the AI assistant connected to Aiku to do it for you, in plain words: "show me the project", "put HELP-123 and TASK-45 under the first milestone", "move the date of the second milestone to next Friday", "post an update: at risk, the supplier is late". It acts as you, with the same rights you have on the page.

Who can change what

The owner, the team members, and engineers who can assign tickets can edit the project (Edit, add or remove work, post updates, change milestones). Everyone else can read it.

Moving a single ticket or task in or out of a project from its own side panel is also open to the people working on it: for a ticket, the people who can update it and its collaborators; for a task, the assignee, collaborators and the person who asked for it. Anyone else can only do it if they can change both the project it is in and the one it is going to.

Related documentation