I can't reproduce it. We have a server override for this field that I landed a while ago (cl/198393239), but it looks like this field is 

Can you please enable chrome://flags/#show-autofill-type-predictions, inspect this field and send me the server annotations? In the DOM, they appear under property "title", something like this:

<input ... title="overall type: NAME_FULL
server type: NAME_FULL
heuristic type: UNKNOWN_TYPE
label: Owner:
parseable name: owner
section: comment_1-default
field signature: 1257707520
form signature: 15555012141081766624" autofill-prediction="NAME_FULL" ...>

After hitting SEND, I noticed we are getting server type "NAME_FULL".

rogerm@: did anything here and our override is being ignored?

title="overall type: NAME_FULL
server type: NAME_FULL
heuristic type: UNKNOWN_TYPE
label: Owner:
parseable name: owner
section: comment_1-default
field signature: 1257707520
form signature: 15555012141081766624"

I removed the owner in order to reproduce the bug.

Note that the form signature is not the same. The structure of the form has changed (an added, removed or renamed field? or more).

The old form was: 5787377393832212605

A fix has been sent: cl/208647764

However, it may take a few days until it gets into effect due to caching. I will leave this open for the moment.

Annotations from the server:

overall type: UNKNOWN_TYPE
server type: UNKNOWN_TYPE
heuristic type: UNKNOWN_TYPE
label: Owner:
parseable name: owner
section: comment_1-default
field signature: 1257707520
form signature: 15555012141081766624

 Issue 832570  has been merged into this issue.

This is what I see from the server now:
overall type: NAME_FULL
server type: NAME_FULL
heuristic type: UNKNOWN_TYPE
label: Owner:
parseable name: owner
section: template_name_1-default
field signature: 1257707520
form signature: 5787377393832212605

Interesting... You are seeing the old form signature (5787377393832212605), you should be seeing (15555012141081766624).

rogerm@: can this be due to caching?

My bit is that there are two (or more) versions of the form (create bug vs modify bug, for example) and you're not both talking about the same one.

In editing this bug, for example, I see:

overall type: NAME_FULL
server type: NAME_FULL
heuristic type: UNKNOWN_TYPE
label: Owner:
parseable name: owner
section: comment_1-default
field signature: 1257707520
form signature: 10934873998177691571

If i create a new issue (which is a different form) I see:

overall type: NAME_FULL
server type: NAME_FULL
heuristic type: UNKNOWN_TYPE
label: Owner:
parseable name: owner
section: template_name_1-default
field signature: 1257707520
form signature: 5787377393832212605

If I edit a launch bug (which has additional fields) then I get:

overall type: UNKNOWN_TYPE
server type: NO_SERVER_DATA
heuristic type: UNKNOWN_TYPE
label: Owner:
parseable name: owner
section: comment_1-default
field signature: 1257707520
form signature: 6214670051844339443

Ultimately, we need as many overrides are there are incarnations of this form.

:(

Maybe we should instead invest in a blacklisting of (crbug.com, 1257707520) instead of ({set of form signatures}, 1257707520)

Could we set autocomplete="owner" on that field?

I'm not sure about blacklisting the field, as there may be a lot of fields with name/id "owner" that we want to fill?