Reporter should not be inherited while cloning the issue

[Vineela Durbha]

I am trying to clone an issue and reporter value is being copied from original issue.

I want the current user value (myself) to be the reporter . I even have Modify Reporter permission even.

Am i missing anything? Can anyone help me on this

[Mark Segall · Accepted solution]

Hi @Vineela Durbha - By default cloning will clone everything, including reporter and there's no native way to simply "untick" the Reporter field.  However, there are a few workarounds:

1. Create a manual automation rule that performs the clone with your customizations.
   • TRIGGER: Manual
   • ACTION: Clone Issue
     • Set your Reporter field to {{initiator}} to ensure the Reporter is always the person who triggered the event
2. Create an automation that executes after the clone:
   • TRIGGER: Issue Created
   • CONDITION (Related Issues):
     • Linked Issues
       Clones
       Are Present
   • ACTION: Edit Issue (Reporter)
     • {{initiator}}
3. Use a marketplace app like Deep Clone. They provide cloning templates

[Vineela Durbha]

This worked @Mark Segall 

[Maciej Dudziak [Deviniti]]

Hi @Vineela Durbha

if you are open to use apps, our app Issue Templates for Jira Cloud does exactly what you need. After installing the app you will have an additional option in the actions menu on issue view called Recreate issue (you will find it above the Clone option). 

It simply clones the issue on your behalf, so you will become a Reporter. It can also clone stories, sub-tasks, links and other issue elements.

Recreate issue action is available right away after installing the app, no configuration is needed. 

[Vineela Durbha]

• Thanks @Mark Segall 

This worked