Many FNC jira ticket types are cloned to cut down on the amount of data entry. When tickets are cloned, the Assignee, Reporter, and approver/manager is inherited from the source ticket. It would be ideal if these fields were blank. Often times the users cloning can not remove the assignee of a ticket, and don't know who the ticket should be assigned to. This is creating confusion when working tickets.
Cloning does what it says - it makes a near identical clone of an issue. The whole point of cloning is that it takes assignee, reporter, manager and all the other fields.
I would very strongly recommend that if you want a copy of an issue with different fields, create a new one and put the right data on it. Stop using clone.
When to use CSV importer When managing your processes in Jira, there are many occasions where you need to create a lot of tasks. Creating them one by one will cost you a lot of time and effort and i...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events