Rally didn't really change much before the purchase either. But the price going up by a lot is why we dropped it.
don't count on whatever work tracker you have is my advice. I've never seen a company stick with one for more, than 10 years. And now I have a lot of code comments about something weird that should not be simplifed because of some bug in the old system. And since closed bugs don't move - and even if they did they get new numbering - I have no ability to look upthat bug and ensure it doesn't break if I need to change the code.
I remember migrating from something else to Jira a few years ago - the guy who did the migration assured me that the old task numbers would be migrated to an extra field in Jira (at my insistence - to avoid this issue).
The old numbers were migrated but of course not displayed anywhere - there as invisible metadata that I assume has since been dropped when Jira was migrated to Jira cloud.
This is why explaining commits with references to Jira or whatever is foolish - always make the source code the definitive reference, for explanations and for documentation. At least at work - maybe other things are ok for public, open development.
don't count on whatever work tracker you have is my advice. I've never seen a company stick with one for more, than 10 years. And now I have a lot of code comments about something weird that should not be simplifed because of some bug in the old system. And since closed bugs don't move - and even if they did they get new numbering - I have no ability to look upthat bug and ensure it doesn't break if I need to change the code.