Thank you Lauren. I'm not normally "cranky" on the forums here, but I can't help but shake my head in disbelief that this thread is marked "solved" when it never has been for me. I appreciate you being on top and aware of the "new" version of the same thing though.
I get that completely, to clarify, I'm marking the case as solved, to match with the internal case status. We are currently on the 3rd internal case for this the prior were marked either cannot replicate or solved. This way we're tracking the right case and keeping the most relevant details. My personal belief is that the issue itself has not been solved for everyone even once, but I have to keep things straight if I'm going to provide you with the best and most relevant information and give accurate updates.
So for transparency sake, my steps are:
Tag the thread with the case when I can associate a thread with one
Mark thread as in progress until the case is ready for a build
When ready for a build mark as pending publication
When in a release version of cPanel/WHM or When the case is marked as done - The thread is marked as solved.
If an issue pops up again with the same issue like in this instance I'll usually note in the new thread - which I did do in this instance.