A Z-Axiss product

Plan the sprint, track the work, know where the hours went.

Boards, backlog, sprints, time tracking and reports for software teams, built and supported by Z-Axiss and designed to take a team from installation to a running sprint in under 30 minutes.

SprintSprint 4
Committed67h
Remaining22h 30m
Days left3
MonTueWedThuFriMonTueWedThuFri
Hours burned down44h 30m of 67h
4 done5 in progress2 to do1 due this week

A sprint you can read at a glance: what was committed, what is left, and how many working days remain.

Overview

Agile project management without the configuration project.

Software teams need sprints, boards, workflows and reporting. Most tools that offer them were built for large enterprises, so setup takes days, the vocabulary needs a glossary, and everyday use is slow.

The portal covers the whole loop for Scrum and Kanban teams: plan, track, log time, report. The defaults work on day one, the power is there when you need it, and it runs on infrastructure you control.

2Board types, Scrum and Kanban, switchable
6Built-in reports, as chart or table
12Dashboard widgets, plus any saved filter
30Minutes to a running sprint, by design
Three roles

Power exists, but most people never have to see it.

For members

Plan it, do it, log it

  • A home page of what is in progress and what is next
  • Move work across the board, edit tickets in place
  • Rank the backlog and plan sprints
  • Log time on the ticket and check the week
For contributors

The tickets they are on

  • Made for contractors and external collaborators
  • Change status, comment and attach files on their tickets
  • Log time against their own work
  • No access to deleting, planning or configuration
For administrators

Control without the clutter

  • People, invites, permission sets and exceptions
  • Project templates, workflows, ticket types and fields
  • Audit log, backups and system status
  • AI provider, usage and limits
The modules

The whole agile loop, one piece at a time.

Modules that share one set of tickets, people and permissions, so a card on the board, an hour on a timesheet and a point on the burndown are always the same piece of work.

Sprint board
Done
In progress
In progress
To do
Boards
The running sprint: to do, in progress and done, with estimates and assignees.
Boards

A board that shows the sprint, not the whole backlog

Scrum boards show the running sprint; Kanban boards show continuous flow with a limit on each column. Cards carry the key, type, priority, estimate and the people on the ticket, and dragging one changes its status.

  • Scrum and Kanban. A project can switch between them and keep its workflow, fields and history.
  • Column limits. A Kanban column turns amber at its limit and red above it.
  • Swimlanes and quick filters. Group by assignee or epic, or narrow the board to your own work.
  • Undo, not confirm. A move shows an undo toast instead of asking permission first.

The stand-up starts from what is on the board, not from who remembers what.

Backlog & sprints
Done
In progress
In progress
To do
Backlog & sprints
A running sprint with its tickets, estimates and statuses, and the epics alongside.
Backlog & sprints

Plan a sprint by dragging, start it with one click

The backlog is a ranked list with the sprints sitting above it. Drag tickets in, watch the hours add up, start the sprint, and when it ends choose where the unfinished work goes.

  • Drag to rank. The order is the priority, with nothing else to configure.
  • Epic panel. Filter the backlog by epic and see each epic's progress beside it.
  • One running sprint. A name, an optional goal and dates; the board follows it.
  • Honest completion. Unfinished tickets move to the backlog or the next sprint, and are counted as carried over.

Sprint planning becomes a short conversation instead of a spreadsheet exercise.

Ticket
Done
In progress
In progress
To do
Tickets
A story with acceptance criteria, collaborators, labels, estimate, sprint and epic.
Tickets

Every field edited in place

A ticket opens with what matters: title, description, status, assignee, collaborators and priority. Everything else sits under More fields until someone needs it, and nothing sends you to a separate edit screen.

  • Types that fit the work. Story, task, bug, improvement, R&D and documentation out of the box, plus your own.
  • Three levels. Epics, tickets and sub-tasks, with links for work that blocks, duplicates or relates.
  • Assignee and collaborators. One person owns the ticket; the others on it stay in the loop.
  • Comments, files and history. Mentions, reactions, attachments and a full activity trail on each ticket.

People stop asking where a piece of work stands, because the ticket already says.

Team timesheet
Done
In progress
In progress
To do
Time & timesheets
The team timesheet for the week, with totals by ticket and by epic.
Time & timesheets

Hours logged where the work is

Each ticket has one estimate in hours. People log time on the ticket itself, remaining time is worked out for them, and the totals roll up to the epic, the sprint and the week.

  • Log in plain terms. A duration such as 2h 30m, a date and an optional note.
  • Personal week. Your week day by day, with the gaps highlighted.
  • Team timesheet. Hours per person per day or week, by project, with totals per ticket and epic.
  • Working days and time off. Burndown, timesheets and reminders skip the days your team does not work.

Timesheets get filled in because it takes seconds, and the export is ready when finance asks.

Burndown
Done
In progress
In progress
To do
Reports
Burndown for a running sprint: committed hours tracked day by day against the ideal line.
Reports

Reports that are already there when you need them

Burndown, velocity, the sprint report, cumulative flow and cycle time come from the work itself. Nobody builds them and nobody maintains them, and each one can be read as a chart or as a table.

  • Burndown. Remaining hours against an even pace, skipping non-working days.
  • Velocity. Committed against completed hours across recent sprints.
  • Cumulative flow and cycle time. Where work piles up, and how long it takes once it starts.
  • Sprint report. What was completed, what was not, and what was added mid-sprint.

Estimates get better because the team can see how the last ones turned out.

Dashboard
Done
In progress
In progress
To do
Dashboards
A shared dashboard: sprint progress, workload, epic progress and cumulative flow.
Dashboards

The view each person actually wants

Every project has a default dashboard. Anyone can build their own from the same widgets, across projects, and share it when it is useful to more than one person.

  • Twelve widgets. Sprint progress, tickets by status or assignee, epic progress, overdue and blocked tickets, and more.
  • Saved filters as widgets. Any saved search becomes a list or a chart.
  • Personal or shared. Private by default; sharing is a permission.

The Monday update is a link, not a slide.

Epic timeline
Done
In progress
In progress
To do
Epic timeline
Four epics across five months, with progress from their tickets.
Epic timeline

The quarter on one screen

Epics sit on a calendar from start date to due date, each with a progress bar filled from its tickets. Drag a bar to move it, or drag an edge to change one date.

  • Progress from real tickets. The percentage is counted, never typed in.
  • Today in view. A marker shows where today falls against every epic.
  • Edit by dragging. Dates change on the timeline itself.

Stakeholders see what is landing when, without a separate roadmap to keep in sync.

Permission set
Done
In progress
In progress
To do
Permissions
The Member permission set: what it allows, group by group.
Permissions

Fine-grained access, in plain language

Admins have full control. Everyone else holds one permission set, which decides what they can do across the app, while project visibility decides where. Each set reads as a sentence, not a matrix.

  • Built-in and custom sets. Member and Contributor ship with the product; add your own for QA, contractors or clients.
  • Simple and detailed views. Switch whole groups on or off, or set each permission individually.
  • Exceptions per person. Adjust one permission for one person without cloning a set.
  • View as. See the app exactly as someone else does, read-only.

Access questions get answered by reading the screen, not by testing an account.

People
Done
In progress
In progress
To do
Administration
People with their permission set, project access, status and last sign-in, plus pending invites.
Administration

An admin area organized by task

People, projects, permissions, templates, branding, settings, the audit log and system status each have their own page. Deactivating or removing someone keeps their history, so time totals and ticket trails stay correct.

  • Invite by email. One person or a pasted list, each with a permission set and project access.
  • Audit log. Who did what and when, with before and after values, kept for a year and exportable.
  • Templates and branding. Project templates for how you work, under your own name, logo and brand color.
  • Backups and status. Daily backups, and one page for email, AI, storage and backup health.

Running the tool is an occasional task, not a part-time job.

AI assistance

One assistant. It proposes, people confirm.

AI is optional. Connect a provider and the assistant is available on every screen; leave it off and every workflow still works by hand.

Write and break down tickets

Describe the work in a sentence and get a drafted ticket, tighten one you already have, or split a large one into sub-tasks.

Plan the sprint

A suggested scope based on past velocity, priorities and who is available, for the team to adjust and confirm.

Triage new tickets

Proposes a type, priority, labels and an assignee for incoming tickets, and flags likely duplicates before they pile up.

Summaries and sprint health

A digest of what changed since yesterday, early warning of spillover, and a summary when the sprint closes.

Draft the timesheet

Finds the gaps in your week and proposes entries from your activity, ready to accept or edit.

Guardrails built in

It acts with your permissions, previews any change to more than one ticket, and every AI change is labeled and logged. Admins set usage caps or switch it off.

Platform & deployment

Built to run on your infrastructure, on your terms.

A complete application you deploy and own, with your tickets, time logs and attachments in a database you control.

RUN

Deployment

Containerized, started with a single command, on your servers or a managed host.

DB

Data ownership

A PostgreSQL database you control, with schema upgrades applied on release and daily backups.

API

Open API

A documented REST API behind every screen, for your own tools and reports.

IN

Import & export

Bring tickets, comments and people in from CSV or Jira; export tickets and time logs to CSV.

SEC

Security

Hashed passwords, breached-password checks, session control, sign-in lockout and optional Google sign-in.

LIVE

Live updates

Boards and backlogs update as teammates work, with undo for everyday changes.

UX

Speed

A command palette, keyboard shortcuts and inline editing for the things people do all day.

FIT

Your brand

Your app name, logo and brand color, in light and dark mode, set from the admin area.

How we deliver it

You are not buying a download.

Z-Axiss implements the portal end to end, and stays with it afterwards.

  1. 01

    Discovery & workflow mapping

    Your ticket types, statuses, fields and permission sets mapped onto project templates first.

  2. 02

    Deployment & import

    Installed on your infrastructure or ours, with existing tickets imported at go-live.

  3. 03

    Customization

    Extra fields, reports, integrations and AI setup from the team that built it.

  4. 04

    Training & support

    Short role-based onboarding, plus ongoing maintenance and upgrades.

Request a demo

See the portal running on your own way of working.

Tell us about your team and we'll walk you through a real project: a backlog, a sprint, a board and the reports that come out of them.

  • A working session, not a slide deck.
  • Set up around your ticket types and workflow.
  • Deployment and import questions answered directly.

Request a demo

We'll reply within one working day.

I'm interested in