Original jira issue and cloned issue comments having mismatch in date and time
3 answers
Hi @Bhushan Naga _ CONT-Type1-THUNDERSOFT INDIA PRIVATE LIMITED _ ,
Indeed the native Jira cloning feature is quite limited and doesn't clone the comment date.
To fix your issue I can suggest trying ou app Elements Copy & Sync that allows to clone issues with all their fields, comments, attachments and more.
It will display the original date and time of the comment like this:
Hi @Bhushan Naga _ CONT-Type1-THUNDERSOFT INDIA PRIVATE LIMITED _
When you use Jira’s built-in Clone action, all comments are technically new objects in the target issue. Jira therefore assigns each cloned comment the current date & time rather than the original timestamp—there’s no way to change that behavior in Jira Cloud.
If you are willing to use a Marketplace app, our app Deep Clone for Jira can help you with cloning your issue comments. Our clone dialog includes a Comments checkbox and an extra toggle Add original comment date and prevent mentioned users to be notified.
So the conversation keeps its true chronology, while Jira still treats the comments as new objects.
Additional perks you might find useful:
- Clone single issues, entire epic trees, or whole projects (up to 100 k issues in one job).
- Optionally include work logs, attachments, issue status, links, votes & watchers.
- Move the clone to another project and automatically create missing versions, components or sprints.
- Presets and post-functions if you need to repeat the process regularly.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.