3 ms·
> "Change 357" could be a sufficient message if there is some other tool to track changes where I can look up what #357 is all about. Realistically, though, yo
by majewsky 9y ago
> "Change 357" could be a sufficient message if there is some other tool to track changes where I can look up what #357 is all about.
Realistically, though, you won't be able to figure out to which task management system this issue number refers, out of the five that your team used in the last 3 years. We have been through two different JIRAs and two different Github trackers in the last 3 years. Sometimes multiple simultaenously.
Also, whenever you write /#\d+/ in a Git commit, GitHub will stubbornly assume that the number refers to Github issues and PRs, even if it doesn't. And some of our repos use both Github issues (for external input) and JIRA issues (for internal planning).
- adrianN 9y agoIf you switch issue trackers every ten months without a migration strategy for old issues that's a pretty serious organizational problem. I hope that's not a mature company.