Automation: Reporter field copy from trigger work item fails on run

[Brian Donaghy]

Hey all, I've been hitting my head on this for a bit now and want to reach out to the wider audience for some sanity checking. I have a rule, that when we move a ticket to a certain status, that it clones the issue in another project, and copies the assignee and reporter on the clone, and links the two issues. I've set up both to be copy from trigger work item, and I'm using the default native Reporter field, but for some reason assignee copies fine, and reporter fails to copy over. The error that pops up in the audit log is "Unknown fields set during clone, they may be unavailable for the project/type. Check your custom field configuration. Fields ignored -Reporter (reporter)" I have the field enabled on all issue types and set to display on all screens. 

I've tried adding another then step to separately copy but that doesnt interact with the cloned issue. Thanks so much for any insight/help!

[Prachi Bolar]

Hello,

Welcome to the community :) 

tried the same automation and works fine 

Could you please validate first, if the correct system reporter field is added to the layout and the issue.

Could you please also validate if you have modify reporter permission as well.

Rest all setup looks fine here

[Mykenna Cepek]

I find it curious that the error you quoted identifies the field as "Reporter (reporter)" rather than just "Reporter". Maybe that's just Jira being weird in the error message, OR it could indicate that you have a custom field (horribly) named "Reporter (reporter)".

Assuming you are a Jira Admin, go to "Admin > Work items > Custom fields" and see how many fields show with the name "Reporter" in them. Remember that the native "Reporter" field will NOT show up in the list of Custom Fields -- it is not a user-added custom field.

If you find such a custom field, I would track down the projects using it, migrate the data to the native Reporter field, and delete that custom field. You'll likely have to remove the field from some configuration for those project.

This is just the first thing I would check. Maybe also discuss with other Jira Admins to help keep this from happening again in your instance. I've seen badly named custom fields like this really confuse users (and even admins) at a number of organizations.