You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I have a customer project for all customer requests. When engineering is foreseeing work they clone an issue from the project and that clone will be worked as normal. I want the original to automatically be update with status as the clone moves through the process.
Any ideas?
Hi Kristi,
No you won't be able to do that with a normal Clone. You could add an automation rule that moves the cloned issue to the same status though.
Hi @kristi gray
Yes, and...to John's answer...
You may be able to do what you ask with an automation rule. Would you please clarify what problem you are trying to solve?
I ask because as you have described the use case, couldn't multiple different clones of the original issue lead to conflicts? That is, to which status should the original issue go?
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.