Find your fit
Who it is for
It is most relevant to a software team that wants issue planning close to code review and builds. A project can contain code, issues and build records, and a board can show a release or sprint without forcing the team to separate planning from delivery history.
It may also suit a team consolidating several related repositories or applications: OneDev supports parent-child projects and shared settings. Teams needing only a lightweight task list should weigh the installation and administration work against the value of its integrated development tools.
The work it supports
Core capabilities
Projects are the container for code, issues and builds. They can be arranged in a hierarchy, which can help organize related products and inherit settings. The issue board then becomes the working view for a project rather than a separate planning service.
Iterations group work into releases or sprints. On a board, a backlog holds issues that are not scheduled into the selected sprint; dragging a backlog card into a state column adds it to that iteration.
Dragging a card across state columns can change the issue state, but only when the user has permission and the configured transition allows it. The product also supports custom states, fields and automatic transition rules, so a team can model its own workflow.
Closing a sprint does not automatically close the issues inside it. The guide describes carrying unfinished issues forward to another iteration while optionally retaining their earlier sprint membership, which helps preserve planning history.
A custom issue board can group open work by an owner field. In the documented example, moving a card between owner columns changes that field; permission to edit the field still applies. This gives teams a second view focused on responsibility rather than state.
Git repositories, pull requests and CI/CD sit beside the issue queue. OneDev describes changing issue state through a commit, build or pull request and showing which build fixed an issue. Use that link when the team needs to trace work from plan to code to result.
A project wiki can keep Markdown documentation with the repository. The Community pricing page also describes opening and discussing issues by email through a service desk, which can be useful when external contacts should not need platform accounts.
Understand the offer
Pricing and getting started
OneDev lists a free Community Edition and a paid per-user monthly Enterprise Edition. Community covers the core development environment and points users to issue-tracker support. Verify the current rate, currency, user count and agreement before subscribing; this profile does not quote a numeric price.
Enterprise adds cluster-based scaling and availability, security and compliance scans, time tracking and broader statistics. Match those needs to the Enterprise feature list before planning a deployment around them.
The installation guide describes Docker, virtual-machine or bare-metal, and Kubernetes paths. Whichever path is chosen, the team should assign responsibility for the server, storage, backups, upgrades, network access and monitoring during its evaluation.
Look a little closer
Before you choose
Set up a small project with realistic issue states. Put a few issues in the backlog, move some into a sprint, try the permitted state transitions, then close the sprint and carry unfinished work forward. This reveals whether the board matches the team’s actual planning rhythm.
If ownership matters, test a custom board with an owner field and a few sample issues. Verify who can move cards between owner columns and how unassigned work appears.
Trace one issue through a commit, pull request and build to see whether the development links are useful. Decide whether the wiki and email issue intake belong in the same operating workflow or need separate access rules.
Before choosing a tier, list the exact Enterprise-only features required, then test the installation path and maintenance duties. Clarify backup and recovery procedures and the final per-user subscription terms for the team’s deployment.
6 distinct sources behind this profile. Research observed Oct 18, 2026. Features and offers can change.
View sources and research →
