Guide
Jira and work management
Jira does almost anything you ask of it, and that is the problem: without judgement you end up with a heavy process people route around. Configuration is a team decision, not an admin one.
Last updated:
Jira is a highly configurable work-tracking tool. Used well, it gives visibility into what is in progress and where it gets stuck. Used badly, it becomes bureaucracy that is filled in to comply and does not reflect reality.
Structure: projects, epics, issues
- One Jira project per product or stable team, not one per temporary initiative.
- Epics to group work with a common goal and a duration of weeks.
- Issues (stories, tasks, bugs) that fit in a few days. If something does not fit in a sprint, it is not ready to start.
Status flows
The default flow (To do → In progress → Done) is enough for most teams. Add a status only when it represents a real wait you want to measure — "In review", "Blocked" — and not just a nuance. Every extra status is another transition someone has to remember to make.
Metrics that help and metrics that mislead
The most useful metric is usually cycle time: how long an issue takes from being started to being finished. If it rises, something is getting stuck and it shows on the board. Velocity (points per sprint) helps to plan within one team, but not to compare teams or as a target: the moment it becomes a goal, estimates inflate.
Integration with Git and CI
Connect Jira to the repository so branches and pull requests link to their issue and the status advances automatically on merge. It cuts the manual work of moving cards and keeps the board reflecting reality without effort.
FAQ
What people ask us
Scrum or Kanban in Jira?
Kanban if work arrives continuously and you prioritise on the fly (support, maintenance). Scrum if you plan in iterations with a per-sprint commitment. Jira supports both; the choice is about process.
How many custom fields should we have?
As few as possible. Every mandatory field is friction on every issue. If a value is not consulted to make a decision, it should not be mandatory.
Are story points useful?
They help to talk about size and to spot when something is not well understood. They are not a measure of productivity, nor a way to compare people or teams.
Can you use Jira without the bureaucracy?
Yes, if the team owns the configuration and reviews it every few months to remove what is unused. The problem is rarely Jira, it is piling up rules and never retiring any.
Related services
Related guides
Next step
Half an hour well spent
Walk us through the problem on a short call. You leave with a first read on how we'd approach it and what it would involve — no commitment, no sales deck.