Is it possible to connect a clone with original epic/story, so if I update the clone the original will be updated automatically as well?
I think it is not a "clone" (after "clone", the two things are de-coupled), but a "sync" (synchronized during their lives).
For syncing issues (Epic and Story are both issues), there are several apps: https://marketplace.atlassian.com/search?product=jira&query=sync
Hi Kerstin,
Yes, you can do that with an Automation rule. If you clone the original using an Automation rule, then you can link them in the same rule.
Then you can create a second rule that will update one issue when the other issue is updated based on the link.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Kerstin Voß hi! You can go with either of the proposed solutions. I'd like to add an additional tool, an external one, that can also help you with the use case. It's a no-code solution, called ZigiOps. It can help you connect your Jira instances and sync them (you can choose which data you want to share between them) in real time. This would mean that whenever there is a change in one of them it will immediately show up in the other. Feel free to explore the ZigiOps platform and if you want to see how it can help you, you can book a demo.
Regards, Diana (ZigiWave team)
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.