During code review, our architect adds comments to the code in GitHub to call out areas that we consider tech debt like spelling errors, layering, poor designs, etc. We are developing a process for dealing with tech debt as part of our overall distribution of work to the scrum teams, but we don't have a good way of identifying and tracking it in Jira.
Granted, creating tech debt stories for things like typos is getting into an extreme level of detail, and we're on a slippery slope towards micromanaging and losing agility because there are those in the org that feel every comment from the code review needs to be corrected, and there are also those within the org that everything anybody does needs to be documented in a Jira issue.
So, here's my question: Is there a way to automate the creation of a user story in Jira from a comment on code in GitHub? This would allow the product owner a way to prioritize the tech debt stories and satisfy those in the org that want every little typo corrected, while showing leadership how much the attention to that level of detail is costing so they can make an educated decision on the path forward.
Thanks!