In Jira, a backlog is a list of tasks or issues that a team must complete within a certain iteration. It is a dedicated space for defining and prioritizing work that a team will take on now and into the future. The backlog is where you plan and prioritize work to be done in future sprints if you work in a Scrum style. If you work in a Kanban style, you can still help your team prioritize upcoming work with a backlog, which is called Kanplan. The backlog contains tasks for a team to work on in a project. It is a convenient place for creating, storing, and managing several kinds of issues, including issues that you’re currently working on and issues which you plan to work on in the near future. The backlog serves as the connection between the product owner and the development team. The product owner dictates the priority of work items in the backlog, while the development team dictates the velocity through the backlog. The backlog of a Scrum board shows the issues for a project grouped into a backlog and sprints. In the Scrum backlog, you can create and update issues, drag and drop issues to rank them, or assign them to sprints, epics, or versions, manage epics, and more.