Cloning the issue clones incorrect information

Question

I am cloning issues across multiple projects and modifying them per each project and per individual ticket.

Cloning logic looks like this:

*  issue #1 contains a description Lorem ipsum
* cloned issue #1 and got issue #2 which contains description Lorem ipsum as well.
* I modify issue #2 description to Lorem ipsum dolor sit amet.
* clone issue #2 to get issue #3. I expect to have description Lorem ipsum dolor sit amet, but instead I keep receiving old description Lorem ipsum in issue #3.

It looks like somehow values for issue #3 are not cloned from its parent issue #2, but issue #1.

Clara Belin-Brosseau_Elevatic · Answer

Hello @Natalia Matsyuk

If you're seeking for an easier way to clone issues and keep the the parent and clone in sync, you can try our app Elements Copy & Sync that allows you to clone and sync a full hierarchy of issues with all their content (summary, description, custom fields, comments, attachments, etc).

You can check our guide here.

The app is for free during 30 days (and it stays free under 10 users).

Kind regards,

Clara

Luka Hummel - codefortynine · Answer

Hi @Natalia Matsyuk,

It sounds like you are experiencing an issue with the cloning process where the cloned issue is not reflecting the most recent changes made to its parent.

If you are willing to try a third-party app, like to recommend trying our Deep Clone for Jira. This app allows for more advanced cloning capabilities and might resolve the issue you're encountering. With Deep Clone, you can:

* Clone issues across projects while preserving all field values accurately.
* Bulk clone multiple issues at once, which is useful if you're managing large projects.
* Maintain relationships between cloned issues and their originals, ensuring that updates are reflected correctly.

Kai Becker · Answer

Hey @Natalia Matsyuk ,

do you clone issues via an automation rule or just the regular Clone entry in the ... menu?

Could you post some screenshots of the process?
If you are using any automation, please post a screenshot of the corresponding rule.

If none of this is the case, I would suggest opening a support case, like Nicolas wrote.