cant create an scheduled automated request to be added daily

Question

I'm trying to create a simple automated job that creates helpdesk tickets each day.

when i check, the audit log i get this error

Action details:

Unknown fields set during create, they may be unavailable for the project/type. Check your custom field configuration. Fields ignored -Category (customfield_10094)Error creating issueCategory is required. (customfield_10095)i cant work out what the customfield 10095 is though... is there a way to find this out..?thanksDavid

Barnali Putatunda_lza0ju · Answer

Hi David,

Seeing the details as you mentioned here, seems like you have multiple custom fields in your JIRA instance named "Category". And you probably chose the wrong Category field (customfield_10094) in your Automation rule to set the value. As per your project workflow setting, you need to set the value for this category field (customfield_10095). I hope once you update that in your Automation rule, it will start working.

Another advice would be, clean up the duplicate custom fields from your JIRA instance, otherwise that will lead to many more confusion like this in future.

If you want to know how to get the Custom field IDs, this documentation will help you to figure that out easily: https://confluence.atlassian.com/jirakb/how-to-find-id-for-custom-field-s-744522503.html

Regards,
Barnali

Nic Brough -Adaptavist- · Answer

Welcome to the Atlassian Community!

The errors you are getting here suggest that you created a Category field, set up an automation to use it, then deleted the field, and then added another one.  Or changed the config so that the newer Category field is in use instead of the old.

You need to do exactly what the error message says, but probably in a bit more depth.  Start with a look at the type of project.

If it is team-managed, you will need to look at all the fields it is using, and correct the automation such that it stops looking at the old Category field and uses the new one.

If it is company-managed, then go to the global list of custom fields and look for the Category field(s), check the field configuration and the create screen - are they all using the newer Category field?