New custom field added and automatically Jira added to automation rule

[Nita Brumbaugh]

Added a new custom field to Jira.  It displays on no screens and it is valid for only one project.   Creating a linked issue through an automation rule utilizing Automation for Jira.   The new custom field was automatically added to the create statement in automation and the linked issue was for another jira project.  

It automatically added the custom field to a random rule which is now causing an error.

This is the 2nd time a custom field was added and an automation rule for a different jira project picked it up and put it in the Create statement.

[John Funk · Accepted solution]

Hi Nita,

That sounds very weird - you should immediately open a support ticket with Atlassian to find out what is going on. Please post back here with the resolution for future readers.

https://support.atlassian.com/contact/#/

[Nita Brumbaugh]

I would love to raise an Atlassian bug, but everytime I go to the link above and enter my bug information, I get redirected to the Atlassian community.  

[John Funk]

Let me see if someone from Atlassian can come here to check on you. 

[Andy Heinzer]

Hi Nita,

When a new custom field is created within Jira, even if it does not appear on any screens, but default that custom field can be a global one.  In which case it could hold a value for any issue in the site.  Unless the custom field has a specific project context setup, then it is likely that this field exists for all issues.  More info in https://confluence.atlassian.com/adminjiraserver/adding-custom-fields-1047552713.html

Did someone setup a default value for this field?  If so, I could see that when issues are created in Jira, that field could be populated as having some value, which would make it appear in Jira, even if users cannot edit/change the value easily because it does not appear on the screen in question. 

I'm not sure that I follow how automation comes into play here?  Could you let me know more about what automation rules/actions are being performed here?

I also don't think I fully understand the error you are seeing here. Could you post a screenshot of that error?

If you were using a Jira Cloud site, I could create a support case on your behalf, however it appears you are using a Jira Server site, in which case the support for your product might be dependent upon the license type you have.  If you have a starter license (3 agents if JSM, or 10 users if JSW), then support for that license is provided here in Community.  But if you have some other license for your site, then the billing/technical contact on that account can still create a support request with us over in https://support.atlassian.com/contact and they would be directed to our main support channel.

Regards,

Andy

[Nita Brumbaugh]

this is the error in automation:

Unknown fields set during edit, they may be unavailable for the project/type.  Check your custom field configuration - Fields ignored.

I know how to fix the error to modify the edit and remove the field.   The issue is that this rule was created a year ago and hasn't been modified since initial implementation.

I added a new custom field for a different JSD feature to Jira and somehow when the jira field was added through custom fields, it automatically added it to this automation rule which makes no sense to me since I didn't edit the rule or anything.

Then the rule starts erroring so I go look at it and it is a field I added several months ago as a custom field for something else.    So totally weird!