nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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

Phil Bustin_7fmhjs

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:

rule errors.png

Do I need to change this to fix the problem?

Accepted answers

All comments

Phil Bustin_7fmhjs

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

Phil Bustin_7fmhjs

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

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_7fmhjs

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.

Configure screen.jpg

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_7fmhjs

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

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud