If an issue is cloned to another project, can changes made to the original issue in the original project be automatically applied to the cloned issue in the new project?
Hello @Adam Abela
If you're seeking for an easy way to synchronize the original issue and its clone, you can try our app Elements Copy & Sync that allows you to clone and sync issues with all their content (summary, description, custom fields, comments, attachments, etc.) and their child issues.
You can check our guide here.
You can try the app for free during 30 days (and it stays free under 10 users).
Kind regards,
Clara
Hi @Adam Abela
What problem are you trying to solve? That is, "why do this?" Knowing that will help the community to offer better suggestions.
Until we know that information...
Although an automation rule could detect and copy some issue updates, it may not be possible to detect all changes. And even when a change can be detected, it may not be possible to accurately synch the changes to a cloned issue. For example: comments, sprint field, fix versions, etc.
Knowing what problem you are trying to solve may narrow the scope a bit from "synch all changes" to something more manageable and possible.
Kind regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The company I work for has two Project Boards: one for deals that have been made (Board 1), and one for post-deal documentation (Board 2). When a deal goes live on Board 1, it gets cloned to Board 2. Since Board 1 is the primary Project Board for the entire Affiliate Team, updates on live deals are made on Board 1.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
From what you describe, perhaps all fields do not need to copy: only the ones with content relevant to the "documentation" work on Board 2.
I recommend mapping out which fields you want to copy to the cloned issue and investigate if those can be copied with built-in features (such as automation rules) or if a marketplace app will be needed to keep issues in sync.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.