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
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
Hi - thank you in advance for any help.
I am working on a Jira Cloud project where we are transitioning from delivery to enhancements. We have a number of tickets that were initially dropped out of scope. These tickets were closed and had the status 'won't do' added. We're now in a position to pick these tickets back up. For business reasons, rather than re-open these tickets the decision was made to clone them and work on them in a new project using the same workflow. However the 'won't do' status has persisted during the cloning process.
Is there a way to remove/reset the 'won't do' status? I have tried progressing them through the workflow and then bringing them back to 'new', but this doesn't remove the resolution.
I've tried cloning issues in both Classic and Next-Gen projects and it clones the issue in the first status in the workflow - as opposed to the status it was in.
Is this the status or the resolution which isn't clearing for you? And is it Classic or Next-Gen?
Resolution in the new issue view appears next to the status, with a green tick next to it. Resolution does not clear during the clone when I tested this.
Hi @Stephen Wright _Elabor8_ - thank you for replying. I should have said, it's a classic project. The status in the cloned issue does clone the first status in the workflow, which is absolutely fine. It is the resolution which isn't clearing when cloning - so yes, it's appearing next to the status with the green tick in the cloned issues.
There is a known bug for this - see: JRACLOUD-75040.
The post-function work-around mentioned in this issue will work for Classic Projects.
To implement this:
^ This will clear the resolution at creation.
If you are using a Next-Gen project - or a Classic Project with a Simplified Workflow - the above workaround is not an option.
Instead, you can achieve the same result using a loop transition automation rule.
Looping back to the same status will remove the resolution.
What this means is the transition will be from the first status, back to the same status. It's cleanest to do this loop transition via Automation.
For the Automation Rule:
A few notes on the above rule:
The second option does require some setup to automate what might be a temporary problem as it's a bug - but it's a workaround which works today for those projects which cannot utilise a "complex" workflow.
@Stephen Wright _Elabor8_ - thank you. I'm glad it is recognised as a bug and not just me. The post-function solution has worked for me. Fortunately we don't have a huge number of affected tickets! I've accepted your answer. Hopefully anyone else with the problem will also find your solutions.
I followed the steps you have provided, but when I clone an epic with sub-tasks, the status of all still gets changed to the default and is not transferred from the original epic. Any ideas what could cause this? The issues are not linked, it is literally just a clone.
Thankyou @Stephen Wright _Elabor8_
I tried adding the automation to the project, but the status is still changed to "Unassigned" (the first status in the workflow, after cloning.
Please let me know if there are any additional steps or if i am missing something.