This question is in reference to Atlassian Documentation: Using the Simplified Workflow
Why is there a backlog step if the kanban board does not use the backlog board?
"Creating a board
You need a board so that you can view and work on issues in JIRA Software. A board displays issues from one or more projects. You can eithera board that someone else has created, or create a new board for yourself. You can create as many boards as you like.
There are two types of boards:
They don't have a backlog Screen but they can have a backlog step.
The backlog is a general term for "the pile of stuff we haven't started to do yet". So when a user creates a new issue, it's in the backlog. That's often "new" or "open" in terms of status, and is also usually on the far left column on boards. Doesn't really matter too much about the exact names - you should use your own language to describe it, but it's still just "stuff we haven't looked at yet"
A backlog in Scrum needs maintenance - estimates, ranking, and then moving into a sprint. So there's a screen for it.
A backlog in Kanban needs nothing. It's just one word that can be used to describe the far left-hand column on a Kanban board.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs