Did I miss something? Why does every thread have 2020 after it?
I am doing my best to forget this god forsaken year and this makes that real hard to do 
2 Likes
We have started to have an issue with using the same names and this website won’t allow it. So it’s been an easy fix to add 2020 so the same names can be used. I agree though, 2020 is not a great year.
CA-LAC-Soledad could not be used until 2020 was added. Because it was used in 2018.
4 Likes
So this fire…
NV-CCD-Numbers-7-2020???
has already been used previously to where the 2020 was needed??
That example no, but I think Folks are just doing it because they see it. Most of the duplicate issues are in CA.
1 Like
So to clarify, if we make a thread and it goes in based on the incident name, it’s good to go. If it won’t go in due to a past fire name, add the year behind it to push it through?
So all don’t need 2020 after it.
1 Like
I started running into this last year I think. I know this will start the “everyone has a good idea” thread, but for me the 2020 is visually jarring the last few days since it’s been added. An odd one here and there works, but every incident it is now just useless visual noise.
Idea?
CA20-TGU-xxxxx
CA20-SHU-yyyyy
3 Likes
Yes, but i think others are doing it across the board. If we add it now it prevents future issues.
2 Likes
There may be a better fix but for now this is it.
1 Like
I found to add an extra question mark works as well.
Ya, I have done that also. But there have been a few that we have already done that. I think the site Admins are looking into it. Put up with it for now until a solution is identified.
2 Likes
Exactly, I know its minor in the grand scheme of things, but visually it makes my head spin. 
3 Likes