I'm trying to confirm this is currently intended behaviour for List Views.
The List route /jira/software/c/projects/<ProjectId>/list explicitly filters out forge manifest provided custom (locked) fields of any type.
What confuses me is if you navigate to the corresponding filter in the filters view, you can add the custom locked field and it displays correctly there so it seems to be a product limitation that could be removed? Backlog views using list views display the field correctly, its specifically the List route / view.
Is there an open ticket for this?
I understand that you are experiencing a limitation in displaying locked custom fields in Jira Cloud List View. Currently, this view automatically filters custom fields provided by the Forge manifest that are locked from displaying.
However, as noted, by navigating to the corresponding filters view, you can add and view these locked custom fields without any problems. This indicates that the limitation is specifically in the List View.
To date, there is no official information regarding an open ticket to resolve this discrepancy. I recommend contacting Atlassian Support to report this behavior and see if any updates or workarounds are available.
In the meantime, alternatively, you can continue to use the filter view to access and interact with your locked custom fields.
I hope this information is useful.
Best Regards.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.