Two quick comments:
That's exactly why I think it's essential to have an easy possibility to move reports around as needed (i.e. let end-users try to make their best guess but without putting any pressure on them) and let more experienced folk sort out the reports which ended up in the wrong tracker.I tend to agree, but have to acknowledge that there's a risk of putting too much burden on end-users to select where to report their feedback, when they may simply not know enough to make that determination. Or at least may not feel comfortable with it.
Here I have to ask for a quick clarification:Part of the argument of the two-layer approach would be to address this by having a one-stop-shop inbox that is friendly and suitable for non-technical users. And then a second layer where the individual items are broken out into more technically detailed repositories which are sensibly grouped in ways that are more manageable for triagers and developers.
As I assume we don't want four trackers