Add a condition that would allow to check if a field exists in a given field context

Issue Summary

It's possible to create automation rules that run globally, on all projects. It's also possible to create contexts for fields to be available only for certain projects. If you have a global rule that edits a specific field, and it stumbles upon an issue where this field is not available, actions, such as Edit issue will throw errors and save them in the audit log. This is expected to happen but it would be great to have a condition that would check if the field is available in the current context. Having such a condition would prevent errors from being saved in the audit log. 

Steps to Reproduce

Follow the instructions as explained in this KB to trigger the error that says:

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

https://confluence.atlassian.com/automationkb/automation-for-jira-rules-update-fields-which-are-not-available-in-the-edit-issue-screen-1283687574.html 

Expected Results

We should have a way to handle exceptions and a condition that would be able to check field contexts should solve this issue.

Actual Results

The audit log will show entries with the "Some errors" status. 

Workaround

A workaround is to add a condition that would make automation not edit a field if the issue is in a specific project: