Required field indicators missing inside Grid and Fluid Fields

[pyrobob83]

Description of the problem
Simple fields that are marked as required don't always show an indicator to users, but sometimes do depending on how they're assigned. Two examples:

1. A standalone URL field:

• Assigned directly to the channel it works fine:

• Assigned directly to a Fluid Field does not:

• Assigned to a Field Group, where the Field Group is used in a Fluid Field doesn't either:

2. A required field inside a Grid doesn't show the indicator no matter how it's assigned, even when the Grid is assigned directly to a channel. Here, Form Handle is a required field and the validation does work, just the indicator isn't styled. There is a wrapped around the column heading, but it just isn't adding the asterisk:

[TomJaeger]

What version of EE are you currently running?

[pyrobob83]

@TomJaeger Sorry, I should've said - latest: 7.3.15

[intoeetive]

@pyrobob83 thank you for reporting this

The "required" toggle for the fields is only applicable when those are used in Channel Entries directly, not in Fluid fields.
Since this is behavior has been around for a while, we're unlikely to change it. However we are planning to give people more control on the fields within Fluid, so might add separate setting there.

We'll get the Grid columns issue addressed

[pyrobob83]

@intoeetive Ah, that makes sense about needing separate settings to make a field required. Ever since sharing fields became a thing, being able to make it required in one place, but not in another has come up for me personally a few times and forced a separate field to be created. In all the examples I can think of though, those were on fields assigned directly to channels (eg News summary being required but Blog summary being optional), so it feels like making that an option wherever a field is reused (whether directly in a channel, directly to a fluid field or as part of field group in a fluid).

Taking that idea a little further, and perhaps this needs to be a separate issue, I'd really like to see the ability to customize the required state, the label and the instructions (which I know has come up in discussions before) for anywhere a field is reused... that'd just be awesome.

CCing @TomJaeger just for visibility on that last part.