change cloning behaviour so cloner is the reporter

using latest version of ScriptRunner and Jira.

3 answers

0 votes

more info reqd

This is actually something I never considered, but would make sense that if I am the one that clones an issue and I wasn't the original issue's reporter, then I would want this new clone issue to be Reported by me.

As cloning is a standard JIRA function though, does this need to be a scriptrunner thing?

I have similar requirement. After cloning any existing ticket, Cloner should  become Reporter for Cloned tikcet

 

Suggest an answer

Log in or Join to answer
Community showcase
Teodora [Botron]
Published Thursday in Marketplace Apps

Jira Inferno: The Nine Circles of Jira Administration Hell

If you spend enough time as a Jira admin - whether you are managing a single, mid-sized instance, a large enterprise one or juggling multiple instances at once - you will eventually find yourself in ...

455 views 1 15
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot