I think we're on our 4th or 5th ticketing system over 15 years. (We're also on our 3rd revision control system, but the code and comments obviously migrated seamlessly across both of the transitions.)

Really? My company is on its third ticketing system.

> Really? My company is on its third ticketing system.

Your company should get it's shit together, unless it's in the business of switching ticketing systems.

Ticketing systems tend to increase in price over time. I know one nameless company looking to migrate after their current system increased in price. Open source isn't any cheaper, you still have to pay admins.

Though one other reason to migrate is the forms are complex and full of required fields nobody understands. Migration will get you past that to what matters, but only for a few years before the groups that required those fields in the first place come back and demand it with the same good but forgotten reasoning as the first time. If this is you, get your act together.

Every company larger than 50 eng I worked for had at least one ticket system migration.

I’ll just let the execs know that we should not allow ourselves to be acquired again, will I?

> Aren't you grasping at straws

That is being generous.

Open Office changing ticketing systems three times. The first time I copied over a few dozen of my most important bugs, the second time I copied over the absolute most important bugs, and the last time I did nothing.

Nobody was reading, triaging, or fixing them anyway.

I've worked on legacy projects which have decades-old tickets.

You can choose to ignore that information: for me it's a treasure, a message from another time.

Sometimes comments are useless crap I can deduce from the code but often I actually get some valuable information.

I won't track down a ticket containing the information unless I'm really desperate.

Unfortunately we live in an agile world and there is not a single doc worth its salt.