so agile question, does your team re-open tickets, move them backwards sometimes, or do you always just clone etc?

In one team we used to move tickets only 'forward' on the board, that caused a lot of cloned tickets. Ultimately it become a mess because ticket release status was unknown. In the other team I saw them moving ticket back and forth, between sprints, even released tasks/stories could be returned to TODO state. In the end it also become a mess, because ticket release status was unknown. 😁

Your ticketing workflow, if properly configured, should be easy to just have a ticket reopened and follow that workflow approach.

cloned tickets are always so much fun with source control integration...