Hacker News new | ask | show | jobs
by bluGill 6 days ago
I find bug trackers and source control fad change several times over the life of my code. A number from a ticket system we no longer use is not helpful.
1 comments
sokoloff 6 days ago
But a number from a ticket system you are using is helpful and vastly more log messages will be read during the time when it’s active than after it’s been retired/replaced.
link
bluGill 6 days ago
The switch was too recent in my case, I'm still seeing many numbers from the old system that I can't look up.
link
ralferoo 5 days ago
You should shout at your project managers then.

The data in the ticket system should be considered important as it's the primary interface through which developers, QA and design share information.

link
bluGill 5 days ago
They have the data but the numbers restarted at 1 and search in the new system isn't good. I think they all agree the old system was better - but the new license terms were unacceptable so we left anyway.
link
sokoloff 4 days ago
Restarting at 1 makes sense only if you think you’re going to run out of integers.

I can’t fathom why part of the deployment of the new system wasn’t to re-seed to the current ticket number or an easy-to-remember integer (hopefully via database, but also ok even if via a Selenium for loop to pull 19,999 tickets to burn the numbers in the new system).

link
bluGill 3 days ago
Different systems have different ways of working. some have one number some start at 1 for different types of tickets. A bug and a new feature have a number of differences.
link