Jira

Jira is Atlassian's issue and project tracking software for agile software teams and business teams, with a free plan for small teams and per-user tiers.

Jira gives a team one shared place to plan work, track each task and see where it stands from first idea to finished release. Atlassian, the publicly listed company behind Confluence, Trello and Bitbucket, builds and sells it. Each piece of work is a work item that moves through a workflow the team defines, shown on a board, a list or a timeline. Rovo, Atlassian's AI, is built in, with search, chat and agents that can pick up planned tasks alongside people. Workflows are drawn as statuses and transitions, and a project can start from a built-in workflow or a blank one. Scrum boards run time-boxed sprints from a backlog ranked by drag and drop, while Kanban boards show a continuous flow. Custom fields add typed data such as select lists, dates and user pickers, and Jira Query Language (JQL) searches can be saved as filters. Jira automation rules fire on triggers such as a new work item or a changed field, then assign work or update it. Plans maps dependencies between teams and spaces on a live timeline, and the burndown and velocity charts report on each sprint. Jira suits software teams that plan in sprints and want each branch, commit and pull request tied to the task it serves. Engineering and product managers who run several teams use Plans to see where one team's work blocks another's. Marketing, design, operations and IT teams can run their own projects on the same boards, lists and calendars. Administrators control access through user roles and permissions, and organisations with rules on where data lives can choose multi-region data residency. A sprint starts with the team ranking the backlog, pulling the top work items onto the board and linking any that block or duplicate each other. Developers put the work item key in a branch name or commit message, so the related code in Bitbucket or GitHub appears on the task. Updates reach the team in Slack or Microsoft Teams, where people can also create and change work without switching tools. Designers attach Figma files and writers connect Confluence pages to the work they describe. Engineering teams with their own tooling use the REST API and webhooks to create work items and react to changes from other systems.