Scrum and Kanban Boards with Backlog in One Project

[LoriAnne Carpenter]

How do you take advantage of the Kanban backlog for a Kanban board in the same project with Scrum boards?

We have two dev teams, each running scrum with dedicated scrum boards in one project. In that same project, we have a Kanban board for our production support team. (We had this Kanban board in a separate project, but needed to consolidate into one project for various reasons).

I had to adjust the project workflow to include a Backlog status (assigned upon creation of an issue) in order to take advantage of the Kanban backlog, but bizarrely this somehow conflicts with our Scrum backlogs. Any issues with status = Backlog do not, in fact, show up in the Scrum backlogs. It's important for our Kanban board to have both a `Backlog` status as well as a `To Do` status, as backlog is where we prioritize, and To Do is the queue for work that's ready for dev.

Is there something I am missing? Have I configured this wrong? 

Thanks in advance!

[Mick d'Ancona]

I believe the resolution to this was that I had manually added some transitions to move to the "Closed" status, but that these weren't explicitly checking the for the relevant "Close Issues" permission. I had retained the default "Close Issue" transition for some steps, so as these default ones were set up correctly, users experienced the correct behaviour in some circumstances, but not all.

Easily solved once identified!

[Mick d'Ancona]

This has now been resolved (and Atlassian support were very helpful). However, as far as I can see, no changes were made - the set-up I have now (which Atlassian confirmed is correct) is, to the best of my knowledge, the same as before the problem was resolved. I suspect user error on my part, but can't identify where