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; } } }

Auto assign Assigne field

joanna.natial

Hello,

I was creating an automation when Project 1 is transitioned to closed it will automate to create and linked project 2 and assignee field will carry over to project 2.

Some work type works, but there are some work types having this issue, please see error on audit log below: Screenshot 2026-02-26 100318.png

The assignee field isa enable to the work type: here is the automation I created.

Screenshot 2026-02-26 100436.png

Please let me know if I have missed something that the automation is having some errors.

Accepted answers

Victor Law - Ricksoft

Hi @joanna_natial

Have you checked the Create screen for the target space/project associated with the Operational (CCG & HC) Payment issue type?

I suspect the Assignee field has NOT been added to the Creation screen in the target project yet, which likely caused the issue.

Here is the official document from Atlassian, but for the Edit work item scenario:

https://support.atlassian.com/jira/kb/some-of-the-set-fields-arent-available-error-in-jira-cloud-automation/

Thank you.

All comments

Victor Law - Ricksoft

Hi @joanna_natial

Have you checked the Create screen for the target space/project associated with the Operational (CCG & HC) Payment issue type?

I suspect the Assignee field has NOT been added to the Creation screen in the target project yet, which likely caused the issue.

Here is the official document from Atlassian, but for the Edit work item scenario:

https://support.atlassian.com/jira/kb/some-of-the-set-fields-arent-available-error-in-jira-cloud-automation/

Thank you.

joanna.natial

Hi, @Victor Law - Ricksoft ,

Assignee field was not added to the create screen, after adding it already works now.

Thank you for the help!

Arkadiusz Wroblewski

@joanna_natial Hello

That audit log message is actually pretty specific:

“The set fields may be unavailable for this space/type. Fields ignored: Assignee (assignee)”

In plain English: Automation tried to set Assignee, but for that target work type (issue type) in the target project, the Assignee field isn’t available on the create/edit config Jira is using so Jira just ignores it and still creates the issue.

That’s why it works for some work types and not others: they’re using different screens/field layouts.

What to check/fix:

In the target project (where the new issue is created), open the work type / issue type that fails and make sure Assignee is on the Create screen / field layout for that type.

Company-managed: Project settings → Screens (or Screen schemes) → the Create screen used by that issue type → add Assignee.

Team-managed: Project settings → Work types → pick the type → Fields → ensure Assignee is added and not hidden.

Have a great Day 🤠

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management