What we left out of Kevta: no sprints, no reporting, no importer

Kevta is an issue tracker without sprints or reporting. No sprint object, no burndown, no velocity, no dashboards, no permission schemes, no SSO. You would find that out eventually. Better here, in five minutes, than in week three of moving a backlog across.

Most of what follows is a decision we would make again. Two items are not decisions at all, and we will say which.

Why an issue tracker without sprints or reporting is a choice

A sprint is not a data structure. It is a commitment to a set of events. The Scrum Guide defines the Sprint as a fixed-length event of "one month or less to create consistency", containing Sprint Planning, the Daily Scrum, the Sprint Review and the Sprint Retrospective, and it names three accountabilities: Developers, a Product Owner and a Scrum Master (scrumguides.org). A team that genuinely runs that should use a tool built around it.

The teams we built for run about two of those five events. A sprint object would give them a container with a date range, and then the bill arrives: a container implies an estimate field, an estimate implies a burndown, a burndown implies velocity, and velocity implies a dashboard read by someone who is not doing the work. We did not lay the first brick because we did not want the building.

What exists instead is plainer: columns you define, custom fields you can use as your own estimate scale, filters and saved views, and the same issues readable as a board, a list, a table or a calendar. If someone asks for a chart at the end of the quarter, Kevta cannot produce one. For some readers that settles it, which is why it is written down.

The rest of the list

Identity is a product, not a login option

You sign in to Kevta with an email and password, or with Google. No SAML, no SCIM, no enforced two-factor.

SSO is the absence most likely to be mistaken for laziness, so it is worth being precise about what it costs. SAML "makes it possible for your users to authenticate through your company's identity provider when they log in to Atlassian cloud apps", in Atlassian's own words (support.atlassian.com). In Atlassian's cloud that capability sits in Atlassian Guard Standard, which "provides capabilities such as single sign-on, user provisioning, user API token management, data security controls, and more". Guard is "a subscription that you purchase for your Atlassian organization", and it is "billed differently compared to your existing app subscriptions" (support.atlassian.com). Enterprise identity is its own product with its own price, not a checkbox somebody forgot.

If your IT policy requires identity-provider login, there is no workaround in Kevta. Same for SOC 2, ISO 27001 or a published uptime SLA. Kevta is in beta.

The two we are not comfortable with

Everything above we would defend. These two we cannot.

There is no importer and no export. The screen exists — Import and export, in workspace settings, with tiles for Jira, GitHub Issues, Trello and CSV, plus a CSV of every issue and a JSON workspace backup — and every button on it is disabled beneath a notice saying there is no server-side job behind them. That is unfinished work wearing the costume of a feature. We left it visible rather than delete it, so nobody meets the gap after signing up.

It cuts both ways, and the second cut is worse. Arriving means retyping. Leaving means retyping too, and a tool you cannot get out of is asking for more trust than one you can. We have not earned that. We are not putting a date on it, because a date is a promise.

So the advice we give costs us signups: do not migrate. Run the next piece of work your team picks up on one Kevta board, beside whatever you use now, and see whether anyone asks to go back. If you have a live backlog of any size, leave it where it is. More on the FAQ.

Who this page is meant to disqualify

If you need sprint reports, permission schemes, SSO, a compliance answer or the Atlassian Marketplace, Jira is the right tool and nothing smaller substitutes for it; our sourced comparison is at Kevta vs Jira. If your complaint is narrower — that keeping Jira configured has become somebody's unpaid second job — that is a different problem, and we wrote about it in the Jira admin nobody volunteered to be.

What is left is a small team, mostly engineers, whose work has code attached and who does not want anyone on it to own a tool. The list above is the price of being built for them.

If that is you, the waitlist gets you an early invite, a founding-member price at launch and a direct line to shape what we build next. The caps and prices live on the pricing page, which counts if this post has gone stale.