This is a must for our business. My OKRs (Goals) track directly to initiatives or epics, and I need that value to copy down to the story level. I do not want to manually enter goals on individual stories. Without this ability, the Goals feature is made significantly less valuable. 

Unrelated but related: why can't native Jira offer the option to have a value entered in a field on an issue at the top of a hierarchy to cascade down to all of its children (and grandchildren)? RIght now I have to program a separate automation per field to have this happen. For example, I want to enter whether an item is tracked as a Capital Expenditure at the initiative level, and then all of its children (epics and stories/bugs/tasks) would also be counted as a Capital Expenditure. Why do I have to write an automation (or two) to make this happen? I also have to write an automation to make sure that if someone edits this field on an epic or story, it is corrected to match the initiative again. It's too much maintenance. This is the same use case as the Goals field. If anyone knows where I can vote on that issue, I'd appreciate a link. 

With Atlassian pushing the (formally) Atlas Teams, Projects and Goals, we need the Goals field to be programmatically accessible via Automation. The current Goals implementation is sloppy and a Rule is needed to apply the Goals value from an Epic to the target Issue, when that Epic is applied to an Issue.

Greetings!

Please provide more context and detail for this suggestion: for which Atlassian products is the field needed, how is it used today, etc.?

When checking the fields supported by the REST API and automation rules, I see the built-in and locked Goals field does appear to be supported.  Please show an example where a rule was tried that did not work with the field, including use of the custom field ID.

Kind regards,
Bill