In 2020-2021 we were finding that cloned jobs retained the created and resolved dates of the original job in the back end which affects our dashboard filters and reporting e.g. the cloned job might show as being created on 11 Feb, but the filters pick them up as the original job date, say 6 Jan, thus throwing out our reporting periods.
They also retain the original resolution status until they are fully closed out again – so while a cloned job may appear as ‘assigned’, the dashboard picks it up as ‘resolved’, again throwing out all our dashboard reporting.
Since then, we have had a blanket internal rule not to clone any tickets.
Does anyone know whether this has been resolved? I am unable to test this at the moment and hoping someone else might be aware if this has been updated.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.