Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,551,802
Community Members
 
Community Events
184
Community Groups

Removing Fix Version value when Cloning a ticket

Is there a way to remove values from select fields when you clone the ticket? We specifically want to remove the Fix Version value when a ticket is cloned.

2 answers

I came up with this today, I hope it helps someone!

 

Locating Hidden Cloned Tickets in Jira

If you clone a Released ticket in Jira, that ticket might not appear on your Board.

Here is a query that finds "hidden" cloned tickets in the XYZ project:

https://<server>/issues/?jql=project%20%3D%20XYZ%20AND%20status%20not%20in%20(Done%2CCanceled)%20AND%20fixVersion%20is%20not%20EMPTY%20ORDER%20BY%20updated%20DESC

 

To fix a cloned ticket:

Delete the value in the ticket's Fix Version/s field.

 

More Information

This situation arises because of two things:

  1. When you clone a Released ticket, the clone retains the original ticket's Fix Version/s value. (It probably shouldn't, but in Jira version 8.20.13, it does.)
  2. Our Board is configured to show only "fixVersion in unreleasedVersions() OR fixVersion is EMPTY".

I am having the same issue. The cloned tickets are defaulting to a "fixed" status when they are created from a closed status ticket. I have not been able to find a solution to this other than having open status template tickets for the types of tickets I create on a regular basis. I'll follow up on with you if I find a solution instead of a work-around.

Brittany Wispell
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Jun 22, 2021

Interesting case, the Clone function should move the ticket back into the beginning status. 

Is this still happening?

Hi @Sarah Bell ,

were you able to fix the issue? I am experiencing a similar issue. Your input on this will be a great help.

Looking forward to hearing from you.

Thanks,

Deepali Bagul

Suggest an answer

Log in or Sign up to answer