Why am I getting errors trying to copy custom fields in an automation?

[Phil Bustin]

My automation to copy custom fields from an issue to a sub-task has this message in the log:

   Create issue

   Unknown fields set during create, they may be unavailable for the project/type. Check           your custom field configuration. Fields ignored -

   Required Testing Regions (customfield_10258), PA Move Time (customfield_10262),               Development Manager (customfield_10232), SQL Regions (customfield_10267), PR Move       Schedule (customfield_10286), SQL Action (customfield_10266), Developer                             (customfield_10233), Software Move Type (customfield_10285)

   Issues created successfully

   TAST6-772

The context for these fields is:

Do I need to change this to fix the problem?

[John Funk]

Hi Phil - you need to show the full Context for the custom field - not the Field Configuration. 

Go to Settings > Issues > Custom fields

Search for the field, click the 2 dots menu to the right and select Contexts and Default Value.

Also, make sure all of those fields are on the Create screen used by the Sub-task issue type for that project. 

[Phil Bustin]

Here hopefully are the screenshots you mentioned.  Please let me know if you need more.  The fields are on both the parent and sub-task transition screens.  There is no Create screen for the sub-task, since the sub-task is always created with an automation.  I doubt that this is relevant, but I renamed the create transition.

[John Funk]

So I see that there are two issue types that are connected with the Custom field. That means that only issues with one of those two issue types will work and not give the error. 

So you need to see what issue type you were using for the Create. 

[Phil Bustin]

I believe I got the same errors when the fields were associated with all issue types.  Some of them may still be.

Issue Types revealed with mouse hover in configuration function

1) Software Move Task Issue Type (sub-task)

2) Dev Story Issue Type (parent)

Dev Story Issue Type shown in Request Tasks transition screen (in parent workflow)

Software Move Task Issue Type shown in Software Move Task Complete transition screen (in sub-task workflow)

Automation rule and log

[Phil Bustin]

Incidentally, why does my log work action not result in the display of the Issue Type or Issue Type name, and is there a better way of trying to display that in the log?

[John Funk]

You need to click the Create button and try to create an issue on the TAST6 project and see if you can populate those same fields. 

[Phil Bustin]

I clicked Create, and I can see the parent issue type, but not the sub-task issue type, if that's what you meant.  That doesn't seem right--that I can't create an issue in the sub-task.  (If you meant the fields in the parent, I have always had values in them when I've tested.)

[Phil Bustin]

For now, I removed the custom field copy functions from the automation, and added them to post functions in the sub-task create transition.  That takes longer to do, but it's working. 

[Phil Bustin]

I found the answer in a similar post: Copy from Trigger issue instead of Current issue.

[Phil Bustin]

Oops--still getting the error.  Thought I saw that it was working.