Jira alternative
Jira can do almost anything, and that is exactly why small teams often dislike it — too many settings for a simple "what are we doing, who is doing it, what is done". In Skillok issues and boards are simpler, modelled on GitHub, and they live next to your code and documents.
In this article
What you get for working with tasks#
- Issues — a markdown description, labels, milestones (the counterpart of releases or phases), assignees, mentions, attachments up to 10 MB, edit history.
- Projects in three views:
- board — columns by status, cards are dragged between them;
- table — all issues as a list with sorting and grouping;
- roadmap — issues on a timeline.
- Custom fields in a project: text, number, date, single select, iteration — that is how you make priority, estimate, sprint.
- Project templates — "Kanban", "Bug tracker", "Team planning" and others.
- Drafts — a card on the board before it becomes an issue.
- Link to code — a pull request closes the issue, and code review happens right there.
What is missing compared with Jira#
- configurable workflow schemes with transitions and permissions on each transition;
- sprint reports, burndown charts, time tracking;
- subtasks and "blocks / depends on" links as separate entities;
- issue templates and automations;
- import from Jira — you can put a CSV export from Jira in a repository, but it will not turn into issues by itself;
- email notifications — only the inbox on the site.
If your process depends on these things, Jira will remain more convenient. If a team of five to fifteen people needs to see who is doing what, a board and issues are enough.
How to set up your team#
- Create an organization and invite the members.
- Create a repository for the product — it will hold the issues and the documents.
- Create a project from the "Kanban" template and add a "Priority" field.
- Mark the nearest releases or phases with milestones.
- Agree that an issue is closed by a pull request — then the board shows not only the status but also the work that was done.
Who it suits#
Small development and product teams that need a clear board and a link between issues and code, not a corporate workflow builder. If all you need is cards in columns, the Trello alternative page shows the board on its own.
Try it on your own task
Create a repository — history, issues and pull requests from day one.
Was this helpful?