Thanks Ian, that was really helpful. I share your concern in particular about the areas of overlap - having to pick a specific repo to assign an issue to is a bit of a pain and easy to do incorrectly (even just talking about myself!).
FWIW - you can actually set label defaults at the Org level, if you are an Org Owner. Of course we could still end up with per-repo customizations - but that seems to be the situation we are already in in Jira, with so many different projects with so many different workflows and labels and components and issue type conventions.
I’m starting to feel like we’re focusing too much on fixing the tooling rather than the processes. We could go through a concerted effort to apply simpler conventions throughout our existing Jira instance.
@ibacher @dkayiwa and others - what if we were to try things in Jira like a simplified workflow process, less issue types? We do need to connect about our process of reviewing the work requests as they come in, maybe when we do that we could also talk about the possibility of simplifying a few things. Perhaps the process conversation is ideal for our TAC meeting this friday.