On this page
Short answer: if you need your issue tracker on your own servers, you have a handful of real options: Jira Data Center, a dedicated open-source tracker, or a project management tool that also tracks agile work. The right choice depends on three things: how much of Jira's workflow and query power you actually use, whether you also plan fixed-date work, and how hard the migration will be. This guide shows how to decide, and where NUSK fits.
Why teams look to host it themselves
- Atlassian ended support for Jira Server. Teams on the old self-managed version had to move to Data Center, to the cloud, or to something else.
- Data control. Some organisations cannot put issue data, which often describes unreleased products, in someone else's cloud.
- Network rules. Internal Jira, Bitbucket and CI servers often cannot be reached from outside.
- Cost at scale. Per-user pricing changes the maths as the number of people grows.
What teams lose and gain when they leave
Be clear about what you are giving up, because that is where migrations disappoint.
Usually fine to leave behind: a long tail of marketplace apps nobody opens, heavily customised screens, and workflows only one admin understands.
Hard to replace:
- Custom workflows with conditions and validators
- A powerful query language that everybody has learned
- A deep ecosystem of integrations
- Years of history and links between issues
What you can gain: a simpler tool, lower cost, hosting on your terms, and a project view that Jira does not give you, such as dates, baselines, cost and risk.
What to evaluate
Score every candidate against this list, using your own data:
| Area | Questions to ask |
|---|---|
| Boards and sprints | Backlog, sprint planning, boards, burndown and velocity? Several sprints at once? |
| Workflows | Custom statuses, allowed transitions, required fields on a transition? |
| Queries | Can you save a filter and share it? Is there a query language? |
| Releases | Versions or releases with progress and notes? |
| Developer links | Commits, branches, pull requests and builds on the issue? |
| Migration | Can it pull issues, sprints, comments, links, history and attachments, and roll back? |
| Identity | SSO, SCIM, MFA, audit log? |
| Hosting | Docker, installer or both? Which databases? Backup and restore? Air-gapped use? |
| Beyond tickets | Dates, dependencies, milestones, cost, risk? |
The options
We built NUSK, so weigh our view accordingly. Here is how we see the field:
- Jira Data Center. Same product, same workflows and ecosystem. The lowest migration risk and the highest cost and admin load. The natural choice if you use Jira's depth heavily.
- Dedicated open-source trackers such as Redmine, OpenProject, Taiga or Plane. Free to run, with real communities. They differ a lot in boards, workflows and scheduling, so test them against your list above.
- Self-hosted commercial trackers such as YouTrack. A closer match to Jira's style, with its own licensing.
- A project management tool that also covers agile work, like NUSK. Fits if your teams do both tickets and plans.
Take any vendor's claim, including ours, as a prompt to test it with your own data.
Where NUSK fits
NUSK is a project delivery tool that covers the agile side of what Jira does, and the planning side Jira leaves to add-ons.
The Jira-shaped parts
- Sprints and boards. Planned, active and closed sprints, several in parallel, a backlog-to-sprint planning view, a Kanban board per sprint, burndown and velocity charts. Closing a sprint moves unfinished items.
- Workflows. Per-project statuses, with allowed transitions and required fields on a transition.
- A query language. NQL is a small Jira-style language:
status = "In Progress" AND (owner = currentUser() OR owner IS EMPTY) AND due < today(7) ORDER BY priority DESC. Saved filters can be shared. - Releases. Group work into releases, see progress and generate release notes from finished items. On the Milestones page, adding an epic to a release brings its stories and tasks along, after a preview of what will be added.
- Developer links. Connect GitHub, Bitbucket Cloud or Bitbucket Data Center. Commits, branches and pull requests that name an issue key, such as
APP-42, appear on the item. Smart commits such asAPP-42 #doneor#time 2h 30mfollow your workflow. Pushing a version tag can release the matching release. - Enterprise controls. Single sign-on (Google, Microsoft, or any SAML 2.0 provider), SCIM provisioning, two-step verification, an audit log with export, and streaming of audit events to a SIEM.
The parts Jira leaves to add-ons
- Gantt chart with dependencies, critical path and baselines.
- Cost, earned value, risk register, and a project health score.
- Deliverables and milestones next to the agile work, so a fixed-date plan and a sprint backlog live in one project.
- Arabic and English, with a full right-to-left layout.
Hosting
- Docker Compose, or a desktop installer. SQLite by default; PostgreSQL, MySQL, SQL Server and Oracle are supported. Backup downloads and a restore path are built in. Internal Jira, Confluence, Bitbucket and CI servers on your own network can be reached.
Where NUSK is not a match
- If you depend on a large marketplace of Jira apps, NUSK will not replace them.
- If your Jira has elaborate workflow conditions, post-functions and automation, expect to rebuild some of it.
- NUSK is a younger product with a smaller community.
Migrating from Jira
A migration is mostly about preparation. The short version (the full plan is in how to migrate from Jira):
- Inventory. Projects, issue types, workflows, custom fields, users, and what you really need history for.
- Create the users first. Assignees and reporters match people by email, so create them or turn on SSO before you import.
- Connect. In NUSK, open Settings > Jira migration and enter the site address and a token. Jira Cloud uses an account email and an API token. Jira Data Center uses a personal access token. The token is used for the import and not stored.
- Pick projects and an approach for each. NUSK creates one project per Jira project, keeps the issue keys (for example
APP-123), and lets you choose agile, hybrid or predictive. - Import in date ranges. For a large project, import a year or a few months at a time. Issues already imported are skipped, so ranges can overlap safely.
- Review the mapping. Map statuses (keep, map, or add as new), people, issue types and the custom fields to keep.
- Apply, check, and roll back if needed. Every import can be rolled back from the import history.
What maps to what
| Jira | NUSK |
|---|---|
| Project | Project (you choose the approach) |
| Epic, Story, Task, Bug, Sub-task | The same work item types; other issue types are kept in a "Jira issue type" field |
| Status | Workflow status (mapped, or added before "Done") |
| Assignee, reporter, watchers | Owner, creator, watchers, matched by email |
| Custom fields | Workspace fields, with option lists merged across imports |
| Sprints, fix versions | Sprints, releases |
| Comments, links, work logs | Comments, links, time entries |
| Change history | Revision history, read-only and not revertible |
| Attachments | Project documents attached to the item (only when you tick "Copy attachments") |
You can also import from a Jira CSV export ("Export > CSV (all fields)") when you cannot give API access. Attachments are not copied that way.
Run a pilot first. Import one small project, compare counts of issues, statuses and assignees, spot-check a few issues end to end, and let a real team use it for a sprint before you move the rest.
Who should stay on Jira
Stay if your team lives in Jira's depth: complex workflows, many marketplace apps, portfolio-level planning across hundreds of projects, or contracts that name Jira. Move if what you mostly need is a solid tracker you control, plus planning and project controls in the same place.
Try a migration on a copy
Pick one project, import a few months of issues, and see whether the board, the query language and the releases feel right to your team. That test tells you more than any feature table.
Start a Jira import · Jira alternative overview
See it with your own project
Import a plan or a Jira project into a free NUSK workspace and judge it on your own data.