cloning issue = the component in the cloned issue is not the same as the original issue

[Rosana Casilli]

Good morning!

I have a quick question. I was cloning an issue with a component = REPORTING. When the cloned issue is finally created, the component field has the component = OTROS. 

Is jira assigning a component when cloning? shouldn't be copied the component from original issue? 

Thanks in advance,

Ro

[Trudy Claspill · Accepted solution]

Hello @Rosana Casilli 

Exactly what steps are you taking to Clone the issue?

Are there any Automation Rules that might be updating the newly created issue?

[Rosana Casilli]

Manualy from the issue

[Trudy Claspill]

Are there Automation rules that might be updating the issue after it is created?

You can check if an automation ran that impacted that issue by clicking on the Rule Execution button in the Details section of the issue.

Also check the Issue History to see if there in any record of the Component value being changed.

[Rosana Casilli]

Hi @Trudy Claspill  

Thank so much for you suggestion. Although there wasn't a manual rule, there was a validation on create issue transition to assign the component that I wasn't aware of. 

I have asked to the owner of this project to redefine  the validation.