Backlog
Backlog Project Management Review and Pricing: Issues and Git
Backlog project management, from Nulab, brings issue tracking, release milestones and built-in Git and Subversion repositories into one project workspace. Developers can connect a Git pull request to its related issue, while the wider team follows the work through boards, versions and milestone planning. That makes it worth considering when you want the discussion, planned release and code review close together.
Its workspace pricing also gives growing teams a different way to budget than a per-person subscription. Explore the issue-to-pull-request workflow and the project limits together to see whether that combination suits your team.
From a reported issue to a planned release
Project administrators set up issue types, statuses, versions and milestones. Versions record releases; dated milestones support burndown planning on a plan that includes charts. A team can therefore discuss an individual defect in its issue and follow the remaining work toward the same milestone.
Backlog hosts Git and Subversion repositories. Pull requests belong to the Git workflow: select a related issue when opening the request, and the issue displays it in a Pull requests tab. This is particularly useful when you want to consolidate repository hosting and planning. If you intend to keep your existing external repository host, check that connection separately before assuming the same workflow applies.
Backlog pricing: choose by projects, charts and storage
Backlog charges for a Cloud workspace, with user or project limits varying by plan. Use Backlog pricing for up-to-date amounts in your currency and billing term. Annual discounts are separate from monthly billing.
| Plan | Main capacity and delivery features |
|---|---|
| Free | 10 users, one project, 100 MB; boards and Git/Subversion |
| Starter | 30 users, five projects, 1 GB; subtasks |
| Standard | Unlimited users, 100 projects, 30 GB; burndown and Gantt views up to six months |
| Premium | Unlimited users and projects, 100 GB; custom fields, unrestricted Gantt view and dedicated support |
Standard deserves a close look when collaborator numbers are growing and milestone charts matter. Premium becomes relevant when custom fields, more projects or storage are essential. Enterprise requires a quote; security services such as Nulab Pass and AI credits can affect the total separately. Ask for a contractual response target if support speed is essential.
Before purchasing for a carefully defined status workflow, ask Nulab to confirm the permitted custom-status count for your selected plan. For external collaborators, configure the actual restrictions. A guest role alone is not read-only, and guest counting on a capped plan needs confirmation.
Set up access and rehearse an import
Admins invite people, assign roles and teams, and can restrict access to adding or viewing issues. Model a developer, project lead and external reviewer before inviting the full team; the permissions need to match how each person will contribute.
CSV batch import handles up to 250 issues at a time and excludes issue status. Parent issues must be in the same file. If you are switching trackers, rehearse a representative batch and plan how to restore statuses and any history the import does not carry. Pull-request email replies also differ from issue replies: replying to a pull-request notification does not post the reply back into Backlog.
Choose the Free plan deliberately if you want to remain on Free. A paid-plan trial lasts 30 days but cannot be downgraded to Free. If running Backlog on your own infrastructure is essential, obtain explicit new-customer availability and service terms before choosing it.
Verdict: useful when planning and repositories belong together
Backlog makes a persuasive case for teams that want issue and milestone coordination with native repositories and a workspace bill. Its appeal is strongest when those repositories will be part of your daily process; evaluate existing-tool connections if consolidation is not your aim.
Compare Jira for configurable issue-to-code delivery with paid cross-team planning, or YouTrack for configurable boards and external VCS/build connections with a separate Server option. The software-team project management comparison can help broaden the choice.
Use a real milestone and one Git pull request to evaluate Backlog, then price the required projects, fields and access. That will tell you more than comparing user limits alone.