"Add field" section on Jira plans showing incorrect spelling of field name

[Arti Patil]

I have create a  custom field "Test" and it is used in Jira and Jira Plans quite extensively. 

However, in Jira plan section, " Add field" filter where we add fields to come on plan it shows as "TTest".
I check custom field section in jira as well as in Jira plan. I edited name and saved again but it did not resolved issue. 
Any idea why it is showing incorrect field name. It is only happening for one field, other fields as coming as is. 

[John Carter]

sometimes jira plans can show incorrect fields if the issue type or field configuration schemes are not aligned across your boards.it might help to double- check that the custom  fields are added to all relevant screens and issue types then refresh the plan that often resolves mismatches like this

[Tomislav Tobijas]

Hi @Arti Patil ,

Have you added this custom field through Plan settings? Instructions for adding/removing a field can be seen here: Add or remove fields from your plan 📚

Also, is the field coming from a team-managed or company-managed space?

One thing that may affect things is UI is duplicated field names (here's one example of a troubleshooting article).
Also, there's this feature request/issue, but it's not that relevant to what you're experiencing. 👀

Btw, I'm guessing all users see the same, and not just you? If it's only you, have you tried using a different browser or incognito mode to see if the behavior persists there as well?

Cheers,
Tobi

[Arti Patil]

Hello Tomislav,
I have already tried adding or removing field from plan. But did not work for. I can see we do not have any duplicate field with same name to cause this issue.
yes, all users are seeing same as me, so conclusion issue with field itself.
However, thank you for suggesting other work arounds. 

[Tomislav Tobijas]

Ah, okay. Thanks for confirming @Arti Patil !

What I would recommend is then reaching out to Atlassian Support. (nothing else comes into my mind atm)

They can probably check what's going on in the backend and fix the issue if there's any.

If you do find a root cause and/or resolution, I'd like to hear it. 👀