With recent discussions about Jira Issue Curation, one side-topic has come up: should we try using GitHub Issues instead of Jira?
Right now, some of our repos in the OMRS organization have issues enabled (most don’t), but if you create an issue in GitHub, it is auto-created as a Jira ticket. (This is why I’m making this a different thread - because whether we use GitHub Issues or Jira, we still have to sort out our issue review/curation process. Having a new tool is appealing because we leave behind some noise and complexity - but ultimately we need people to like using the tool so we’re comfortable reviewing issues regularly.)
Several people expressed interest in GitHub issues. Both the FHIR and MF Squad expressed interest in piloting it, but wanted to know what this might look like. I’ve taken a first attempt at summarizing the pro’s and con’s and how it might look if we tried using GitHub issues. We went through this quickly in the PM Squad call today but would like to share and discuss further here.
tl;dr: GitHub issues is much simpler than Jira. We would lose a lot of complexity which may not be a bad thing, but will take some getting used to. Being in one place and the simple automation is appealing. There are add-ons we can buy if we want to regain some of the complexity and project management tools that are in Jira.
Curious to hear if people have any thoughts, or experiences from using GitHub Issues to share