Has anyone noticed that new fields created in Next-gen projects impact existing Filters?
Scenario:
- A custom field - 'Stream' was created in one of our Next-gen projects.
- This field already exists as a generic custom field across our Classic projects.
- Existing Filters that referenced the generic custom field were broken and stopped working
Does anyone have any feedback on this? Has it been raised with Atlassian?
