It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

change cloning behaviour so cloner is the reporter

James Fishwick May 09, 2016

using latest version of ScriptRunner and Jira.

4 answers

1 vote
Geoff Wilson May 12, 2016

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?

0 votes
JamieA May 09, 2016

more info reqd

0 votes
Sanjay Dalvi Sep 20, 2016

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


0 votes
Benjamin Peikes Apr 11, 2019

Cloning in JIRA is completely broken. They claim that the reporter will be changed if the user performing the clone does not have permission to change reporter. How that makes sense, I have no idea.

We've also not had consistent results with cloning tickets. It's basically useless.

Suggest an answer

Log in or Sign up to answer
This widget could not be displayed.
This widget could not be displayed.
Community showcase
Posted in Jira Core

How to manage many similar workflows?

I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...

747 views 7 0
Join discussion

Community Events

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

Events near you