change cloning behaviour so cloner is the reporter

using latest version of ScriptRunner and Jira.

3 answers

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 Sign up to answer
Community showcase
Asked Thursday in Jira Ops

I'm John Allspaw, Ask Me Anything about incident analysis and postmortems

I'm John Allspaw, co-founder of   Adaptive Capacity Labs, where we help teams use their incidents to learn and improve. We bring research-driven methods and approaches to drive effective inciden...

4,681 views 20 14
View question

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