We are a small team mostly focused on medium to large scale websites. I am going to merge all issues for all of our projects into one backlog using Kanban with JIRA. The idea being that no one gets to pick and choose what they want to work on, but rather we can prioritize everything that the company needs to do and everyone will work on their next ticket in the que.
This will lead to hundreds of tasks in my backlog. I'm fine with this when it comes initially importing all the tasks for a project and prioritizing everything. However my quandary is as new issues are created by the team (through testing or just new things that come up) and go into my backlog what is the most efficient way for me to handle these without loosing track of what items I need to prioritize? Do I prioritize those right away? daily prioritize new items? have them go to some pre-qualified status to help me easily see what are new issues that need be entered into the backlog? or some other method that someone far wiser than I has already developed? thanks for any help.
Backstory if it's helpful: We are a team of 8. In the past we have had a serious issues with handling projects separately as well as new projects separated from ongoing support for current clients. Obviously there has been zero true project management. Thus leading to the person who is responsible for ongoing clients to yell about their tickets be priority and likewise for the person trying to coordinate our new projects to scream that developers should be working on those first. Thankfully we are fixing that. Since I've been the most vocal about it, I get to play PM. I don't want to just play PM though. I'm doing my best to study many methods, read on here, and learn from others. I've chosen Kanban because I think it helps keep the flow going (there's always a flow of issues in our team), easily see what's the priority across the company, handles efficiency and resources with WIP limits, and makes sure that everyone knows what is the next thing they should be working on.