Kanban with your own columns
Each company defines the board stages, for tasks and for projects, and drags the card between them.
Projects module What support uncovers
What support uncovers
turns into delivery
Projects, epics, sprints and recurring tasks — with the originating ticket always one click away and the pull request linking itself to the task.
- Unlimited users
- Kanban with your own columns
- GitHub included
How work moves The tool adapts
The tool adapts
to your process
The columns, the types and the deadlines are the ones your company uses — not the ones the software decided were best.
List, board and Gantt
List and board for tasks, and a timeline (Gantt) in each project.
Epics with progress
Group tasks into epics and watch the bar move. If the epic grew too big, it becomes a project.
Sprints by department
One active sprint per department, with burndown and velocity. Whatever did not finish rolls into the next one.
Recurring tasks
The routine appears on its own on the right day, with pause, resume and closing — nobody has to remember.
Deadlines that warn you early
The project deadline sends a heads-up three days before, on the day and once late. A late task goes to the project owners.
The bridge to Support The ticket does not die
The ticket does not die
in a report
The people who answer and the people who deliver work off the same base. What the customer asked for reaches the backlog with context, and goes back to them when it ships.
- One click turns the ticket into a task, keeping the link between the two
- Subjects that keep repeating become a single task, and go "delivered" when it closes
- Cross-references with # between tasks and projects; an @mention notifies the person
- Blockers logged on the task, with a linked approval request
- A public task link to show progress to people outside the system — revocable
- PDF and Excel reports carrying your company's brand, valid for 7 days
The code comes back to the task
The task key in the branch name, in the pull request title or in its body links everything by itself — no plugin, no pasting links.
Sprint routine Plan, run
Plan, run
and close
- 1
Plan
The backlog already carries the themes support raised, with the number of tickets behind each one.
- 2
Run
Board by stage, dependencies between tasks, hours worked and stakeholders following along.
- 3
Track
A live burndown and deadlines warning you before they blow, not after.
- 4
Close
Whatever is left moves to the next sprint, velocity goes on the record and the release note ships through the API.
GitHub An integration that links
An integration that links
itself
A branch from the task
Create the branch with the task key already in the name, exactly the way your team agreed.
Linked pull request
The PR shows up on the task with its current state: open, draft, merged or closed.
The organization owns the link
The connection belongs to the organization, not to a person. Whoever leaves the company does not take the integration with them.
A repository per project
Each project points at its own repository, and the history stays where the team goes looking for it.
Questions about Projects
Can I buy Projects on its own?
You can. The plans on the site include both modules; if your company wants Projects only, talk to us and Support leaves the menu. Teams, customers and products come with any contract.
What about the bridges to support, if I only have Projects?
They simply do not appear. No menu leading to a locked screen: what you did not buy stays out of the way, with a discreet invitation if you want to take a look.
Are the board columns fixed?
No. Each company defines its own columns, for tasks and for projects, and they apply to everyone on the team.
Is the public task link safe?
It is an address with a random code that shows progress only, with no internal data, and it can be revoked at any moment. It is rendered on the server, so it also works in WhatsApp previews and for AI agents.
Connect support to delivery
Start with the module that solves the pain you have today and add the other one when it makes sense.