> I would not ask/expect Tomoko to do this migration. If that really is > influencing people's minds here, I volunteer to try to create/iterate the > tool that can migrate Jira issues to GitHub, if we can agree that keeping > our full history is worthwhile/important. >
Ahem... You're right. It wasn't my intention to put the heavy burden on Tomoko, sorry. > So far it looks like I'm one of maybe only two devs passionately against > throwing away the rich history in our issue tracker. > This is the bit we clearly have a different opinion on - I don't have a problem with part of the history staying in Jira. I do accept your argument about searching through history using one user interface though - this indeed would be useful. > Maybe it is because I am too old and have come to value history too much ;) > This is overdramatic. It'd be different if Jira were to be removed but it's not - it's staying. There are a million links around the web pointing at those Jira issues. Blogs, code, etc. If you create a copy in github and people start commenting on those issues in github then those links point at a stale state... So not only we'd need a link from github to jira... we'd also need a link from jira to the (new) github issue and a freeze on any changes in Jira after that. > Say two years from now we want to migrate to XYZ issue tracker. Would we > choose again to discard past issues (Jira and GitHub issues)? > I'd be more afraid of what happens to github issues in two years (or longer). Will it look the same? Will it be different? Will it be gone (and how do we get a backup of the isse history then)? Contrary to the apache-hosted Jira, github is very much an independent entity. If Elon Musk decides to buy and close it tomorrow... then what? :) Dawid
