Automation : change reporter for cloned issue
Asked by Tatianna Volamena:

Hello,

I would like to change the reporter when we clone a task.

I went to automation and create a rule, but as you can see below on the dropdown for "Edit Issue" I don't have the option to put the reporter as the person who created the ticket.

Thanks

![automation_reporter.PNG](https://community.atlassian.com/t5/image/serverpage/image-id/199964i2998D4B9843298D6/image-size/large?v=v2&px=999 "automation_reporter.PNG")


Answers:
author: Dan Tombs
body: Hi [@Tatianna Volamena](/t5/user/viewprofilepage/user-id/4952964)

You can use a smart value. Reporter and creator are two separate values so you will need to use {{issue.creator}}. This should then populate the reporter with whoever cloned the issue.

Kind Regards,

Dan Tombs

comments: author: Dan Tombs
body: Hi [@Tatianna Volamena](/t5/user/viewprofilepage/user-id/4952964)

Please see screenshot

![Capture.PNG](https://community.atlassian.com/t5/image/serverpage/image-id/199971i20DCF2A0B38A8BE9/image-size/large?v=v2&px=999 "Capture.PNG")


author: Tatianna Volamena
body: Hi Daniel,

Thanks so much.

When a "task" is cloned, the reporter is now the person who created the ticket.

![test3.PNG](https://community.atlassian.com/t5/image/serverpage/image-id/200103i5F13B44FC92ACF14/image-size/large?v=v2&px=999 "test3.PNG")

Cheers


author: Tatianna Volamena
body: Hi Daniel,

Me again :).

I have activated the rule and noticed an issue. Indeed. instead of creating only "one" clone, it creates "**two**" clones of the same task.

I suspect this is caused by the 1st trigger "when issue created". I looked around but I couldn't find a trigger "When issue cloned"...

Any thoughts ?

Thanks in advance


author: Stefan Salzl
body: Hi [@Tatianna Volamena](/t5/user/viewprofilepage/user-id/4952964) and welcome to the community,

just to make sure we are on the same page:

as I see in your rule the trigger is ?when issue is created" and not ?when issue is cloned".

So let's say there is issue A that geta cloned to issue B. which user is appearing as reporter right now in the cloned issue B? and which user would you like to be in issue B? the same as in issue A?

Best  
Stefan

comments: author: Tatianna Volamena
body: Hello Stefan,

Without the automation rule, the reporter remains the person whoever is originally the reporter in the task A. However, what I want is that the reporter becomes the person who is cloning the task.

Now I am getting that result thanks to the help of Daniel.

Cheers


author: Tatianna Volamena
body: Hi Daniel,

Thanks for your feedback. Not sure I understand what you mean though...

I did try to do this but it doesn't work. If it is ok, would you mind to give me details steps or screenshots to help me get the rule right.

Thanks

![test 2.PNG](https://community.atlassian.com/t5/image/serverpage/image-id/199967iEE5E26569D333B43/image-size/large?v=v2&px=999 "test 2.PNG")

comments: author: Dan Tombs
body: Hi [@Tatianna Volamena](/t5/user/viewprofilepage/user-id/4952964)

You'll need to do two things. Since you are creating the rule from the original issue rather then the cloned issue you will need to include a branch after the clone action. Then set the branch to recently created issue.

Move the assign issue action into the branch and then in the reporter field add {{issue.creator}} rather then adding in the additional fields section.

That section is for more advance settings using JSON which we do not need to do here.

Hopefully this helps.

Dan


author: Tatianna Volamena
body: Hi Dan,

Thanks for the feedback.

Here is what I did based upon what I understood from your feedback. I did publish my changes but it still creates 2 clones vs 1.

![Clone.PNG](https://community.atlassian.com/t5/image/serverpage/image-id/201516i67538F3F8100BE96/image-size/large?v=v2&px=999 "Clone.PNG")

Thanks