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

Receiving error on Automation for Assignee of a auto created subtask

Steven Lloyd_4xxk2v

I have been looking to set up a rule when transitioned a sub task is created and assigned to a user in a custom user picker field. This seemed to work fine at first, when trying to add some additional automation rules it then stopped. I have disabled all other rules and cut a shorter automation rule to allow this to run but I keep getting the below error message;

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

I have set this to a global and a project level automation rule but still no success, I am not sure what was changed to cause this to stop working, the Assignee field should take from a specific user field and as mentioned this had been working previously.

Accepted answers

Steven Lloyd_4xxk2v

Answering my own question.

Should have stepped back and taken a minute before posting.

I had amended the create screen and removed the assignee field as I wanted it to auto assign, this is why it wasn't processing

Steven

Ashkan Malekly_4jfgcl

Hii @Steven Lloyd

consider some items for running automation:

1. The actor of automation have assignee permission.

2. When you want create sub task which field is required and you must fill it by automation.

3. The actor of automation be in project role that has the first item permission.

4. On your sub task workflow check the conditions and validation that must pass to create sub task.

5. The custom field configuration must be include your project and your issue type.

if all these items pass please send screen shot of your automation

All comments

Steven Lloyd_4xxk2v

Answering my own question.

Should have stepped back and taken a minute before posting.

I had amended the create screen and removed the assignee field as I wanted it to auto assign, this is why it wasn't processing

Steven

Ashkan Malekly_4jfgcl

Hii @Steven Lloyd

consider some items for running automation:

1. The actor of automation have assignee permission.

2. When you want create sub task which field is required and you must fill it by automation.

3. The actor of automation be in project role that has the first item permission.

4. On your sub task workflow check the conditions and validation that must pass to create sub task.

5. The custom field configuration must be include your project and your issue type.

if all these items pass please send screen shot of your automation

Steven Lloyd_4xxk2v

Thanks for the reply Ashkan,

I was working with too much yesterday and changing little bits here and there so by the time it came to running through I didn't have a clue which change had impacted it, my own fault that one for trying to rush through it.

Cheers I appreciate the response as that too is correct

Poat

Wow.. I also made a ton of changes, one which included cleaning up the create screen. It wasn't clear in the error that this was the issue, as the field was a common field on the issue type itself. Thanks for saving me more hours of digging!

Daniel Rojas_vpea8z

Save my day!!!!. I created a new screen for a specific project and haven't added the assignee field to the new create screen.

Thanks

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-software

automation