Forking discussion on - Some folks have 100+ issues assigned - Jira components might not be the best way to get things triaged
I just ran a built-in Jira report to summarize how many tickets are claimed by different users [1]. It does look like component owners tend to accumulate issues and they are not likely to get addressed. So what do we want and how can we make it happen? Here is what I want, personally: - every new issue gets looked at by someone who can decide the right component, who to ping, etc - no person is assigned an issue that they are not active on - we don't release with potential bugs waiting to be triaged The current status it that issues get assigned to a component owner when filed. The component owner should route it and it most likely will end up in some component unassigned. Another possibility is that we add a "Needs Triage" status and figure out a way to make sure they are all looked at - maybe also by blocking a release on having zero Needs Triage bugs. Just an idea. And important question I did not look into: what do other Apache or Apache-style decentralized projects do? Kenn [1] https://issues.apache.org/jira/secure/ConfigureReport.jspa?projectOrFilterId=filter-12343976&statistictype=assignees&selectedProjectId=12319527&reportKey=com.atlassian.jira.jira-core-reports-plugin%3Apie-report&atl_token=A5KQ-2QAV-T4JA-FDED%7C4ba437528000034c87065a99ddea7c1ea92342aa%7Clin&Next=Next
