Content field created by Agent does not have translation option

MR raised.

Made the field storage translatable by default.

If the user prompts to make the field translatable, then it would be marked translatable. If they don't, then it would be disabled.
But without the MR, the option for marking translatable does not appear only.

The issue is reproducible.

@vivek panicker
I have reviewed the functionality.

Steps followed:
Enable translation on the site, configure a new language for content types
Add a chatbot with Field Type Agent enabled
Ask the chatbot to add a field to any content type
Inspect the field

Actual output:
Chatbot responds that it has set the field as translatable.
But no "Users may translate this field" option found in the newly created field settings.
When the content is translated the new field value is not translated.

SS attached.

@anjaliprasannan Not sure why it did not work for you, I have tested this thoroughly and it worked fine for me.
Can you confirm the patch got applied for you?

After applying the patch successfully:
- clear cache
- ask chatbot simply to create a new field on a content type
- go to the field settings and see that you have the "Users may translate this field" option

Can you try the above?

@vivek panicker I tried in new installation still and same steps as above, I do not get the translation field in field settings.