How can I show all Jira work items on the Board instead of a separate Backlog?

[haran anjioni]

Hi,

Currently, my space has both a Backlog and a Board. All new issues are added to the separate Backlog list, regardless of their status.

I want all work items to appear directly on the Board.

New work items should be created in the TO DO column, and I would like to manage my backlog as a status column on the Board for tasks I manually postpone.

How can I configure this?

Tnx!

[Marc -Devoteam-]

Hi @haran anjioni 

What type of space are you using Team or Company managed and what type of board, Scrum or Kanban?

If a scrum board is used, there is no option to see all on a single board, you will need a kanban board for this.

[Rudy Holtkamp]

Hi @haran anjioni ,

This

Currently, my space has both a Backlog and a Board. All new issues are added to the separate Backlog list, regardless of their status.

tells me that you are using a Scrum board.

If you want newly created issues in your sprint, you can add an automation which fills the sprint field  with the current running sprint.

The automation can look something like this:

But you should select 'Active sprint' for you board name.

(Update)

You also might want to add a transition to a status which is in the first column of your board (e.g. To do)

I hope this helps,

Rudy

[haran anjioni]

Tnx

[haran anjioni]

Tnx

[Germán Morales _ Hiera]

Marc and Rudy are pointing in the right direction. Two things to add.

The Board / Backlog split is by design in Scrum boards. There's no setting that merges them, and trying to force it usually makes things worse.

So either:

1. Switch to Kanban. One view, every item in the filter, your "manually postponed" idea becomes a status mapped to a board column. Lower friction if sprints don't earn their keep for your team.
2. Keep Scrum and auto-add new items to the active sprint. You don't need a JQL lookup. In the Edit work item action of an Automation rule, the Sprint field has a dropdown that lets you pick "Active sprint" on a specific board. So the rule is:
   • Trigger: Work item created
   • Condition: Project = your key
   • Action: Edit work item, Sprint, Active sprint on board [your board]

That's it. New items land in the active sprint without further config. Official KB: support.atlassian.com/jira/kb/how-to-add-newly-created-issues-to-the-active-next-sprint-using-automation

One caveat. Anything pushed into the active sprint mid-flight will count toward burndown and capacity. Fine for most teams, worth knowing if yours is strict about sprint scope. If that's a concern, the Kanban route is cleaner.