Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,294,705
Community Members
 
Community Events
165
Community Groups

Automation : change reporter for cloned issue

Edited

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

3 answers

1 accepted

2 votes
Answer accepted

Hi @Tatianna Volamena

 

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

Hi @Tatianna Volamena

 

Please see screenshot

Capture.PNG

Hi Daniel, 

Thanks so much.

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

test3.PNG

Cheers

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

0 votes
Stefan Salzl Community Leader Jun 01, 2022

Hi @Tatianna Volamena 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

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

Like Stefan Salzl likes this

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

Hi @Tatianna Volamena

 

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

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

Thanks

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Atlassian Automation

Jira Automation: Sum Up Story Points Roundup (Initiatives -> Epics -> Story/Tasks -> Subtasks)

Hi Everyone, In this roundup we combine all the jira automation rules to sum up story points across different issue types. We start from the lowest level, summing up story points from sub-tasks t...

1,786 views 2 7
Read article

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