Automation thinks field is unavailable for project type
Asked by caglad:

I have a field that I am using in global automation to fill in the value. But error log suggests this field is not available for my project type. However, the issue type shows available for all issue types and available globally for all projects. I am able to use it in an import for project type but automation doesnt like it.![storypointserror.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/332512i1A09812380826C6B/image-size/large?v=v2&px=999 "storypointserror.jpg")![storypointsissuetype.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/332513i47BFDB6C85A40AA6/image-size/large?v=v2&px=999 "storypointsissuetype.jpg")

I have to be missing something.. welp


Answers:
author: caglad
body: Jira Cloud -

Here is the rule.. Create issue - from trigger issue - and everything is being created with the correct values except for this.

![rule2.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/332556i7DC30762D8D4B00B/image-size/large?v=v2&px=999 "rule2.jpg")![rule1.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/332557iF9F834788D1A247E/image-size/large?v=v2&px=999 "rule1.jpg")

omg dont tell me its because I didnt put the brackets in

comments: author: Julian Governale
body: Since it works from Import i assume it is on your create screen for that project and the task issue type but here are a few aspects to double confirm.

1. The field **Story points (Est. Hours)** is present on the task issue type create screen
2. If it's not present
   1. Ensure it's added to the Create screen
   2. Ensure it's not marked as hidden in the field config
3. Confirm you don't have two fields with the same name in the system
   1. If you do, confirm you have selected the right field in the automation (customfield_10014)

If all the above is confirmed, try to set the field through the additional field section. First, remove it from the "Choose fields to set" area to avoid any conflicts.

```
{
"fields": {
  "customfield_10014": 2
   }
}


```


author: Bill Sheboy
body: Hi [@caglad](/t5/user/viewprofilepage/user-id/3616945)

Please post an image of your complete rule and the Create Issue action. These will provide context to compare to the audit log details you show.

And, which version of Jira are you using: Cloud, Server, or Data Center?

Until we know that information...

I wonder: does the Create Issue action select the project and issue type explicitly? If not, that may be causing a problem with the field.

Kind regards,  
Bill

comments: author: Bill Sheboy
body: [@caglad](/t5/user/viewprofilepage/user-id/3616945) please try to stay in *one thread when responding*. That will help others reading this question in the future know if there are multiple solution approaches. Thanks!

Please post your complete automation rule, in one single image. That will provide context for where the Create Issue action is happening within the rule.

Which version of Jira are you using: Cloud, Server, or Data Center?

If Jira Cloud, what type of project is this: company-managed, team-managed, etc.?

Is your custom field visible on the views for creating an issue?


Tags: error