Why are custom field values (e.g.Owner) visible on issues but showing as blank in Team-Managed Jira

[M Chandra Shekar]

In a Team-Managed Jira project, some custom fields are showing values on the issue view, but the same fields appear blank in Issue Navigator filters.

For example, the “Owner” field is added to the issue layout and contains data, but when added as a column in a filter, the Owner value is blank.

What could be causing this, and how can it be resolved?

[Bill Sheboy]

Hi @M Chandra Shekar 

Please post the JQL you are using in your filter. 

If the JQL is ambiguous such that it returns work items not in the project with the team-managed project (TMP), People field, those would be empty values.

Kind regards,
Bill

[M Chandra Shekar]

Simple JQL I used eg. project Name=ABC And Work Type = Req and added required columns related to that work item. But one of the field data was not showing, As it’s blank. I have added a correct column that used in issue layout.

[Bill Sheboy]

Are all of the "Owner" field values empty in that view or only some of them?

When you ask a teammate, are other people seeing this symptom also?

[M Chandra Shekar]

Completely it’s blank, no data showing. Same for others.

[Bill Sheboy]

One more thing to check, aligned with the ideas from @Marc -Devoteam- 

Unfortunately, there is nothing in Jira to prevent creating multiple fields with the same names, both globally (i.e., company-managed) and in team-managed spaces.  And, it is possible to accidentally select fields at different scopes within a TMP...leading to strange results such as one field has data in views but not in JQL searches, automation rules, etc.

The way to check that is to either work with your Site Admin to check for global fields with the same name, or from the TMP settings check if there are multiple fields where one of the field types is a User Picker (i.e., a global field) versus a People (i.e., a TMP field).

[M Chandra Shekar]

Used some differently unique names but it’s not working .

[Bill Sheboy]

Did you try using the custom field ID in place of the field name in the JQL?  That will confirm if the problem is the wrong field is being accessed.

To find your custom field ID, let's use a REST API endpoint:

• identify an example TMP work item with your field where it has data in it 
• when logged into Jira, open another browser tab
• enter your Jira URL and the key to read for the item's data 

https://<yourJiraUrl>/rest/api/2/issue/<workItemKey>?expand=names

• Search on the page for your field, such as with Control-F (find)
• Confirm the field has your expected value
• Use that custom field ID in your JQL

[Marc -Devoteam-]

HI @M Chandra Shekar 

Is this field created as a custom field in Jira administration or as a custom field in the team managed project?

Also you can't set context on this field if you want to use this in Team managed projects.It needs to have a global context for all projects.

[M Chandra Shekar]

Hi @Marc -Devoteam- it’s created in Team managed project.