Issue Summary

When creating a Team-Managed using the Import Data option, the system generates a board filter that is visible and editable — which contradicts the standard behavior of Team-Managed (TM) projects. This filter is not properly scoped to the project (scope is left unset), and is instead treated as a global filter. This results in unintended access control behavior and the board being inaccessible to other project members unless permissions are manually modified.

Steps to Reproduce

Step 1: Go to Create Project > Import Data

Step 2: Choose Jira (Business Project) from the import options and follow the prompts to complete the migration into a Team-Managed Software Project

Expected Results

• A Team-Managed Software project should be created with an internal board filter, not visible or editable by users.
• Permissions to access the board should be managed via project access roles, not filter viewer/editor permissions.
• No user-facing filter should be created or associated with the board.

Actual Results

• A new user-visible filter is created with the name Filter for <Project Name> board and the description Default Filter, generated during External To Cloud migration.
• The filter is not scoped to the project (scope field is unset).
• Filter viewers are set to Unknown Project, and editors are private.
• The board becomes inaccessible to all users except the one who performed the migration.
• Board access must be restored manually by updating the filter permissions, which shouldn't be necessary for TM projects.

Workaround

A temporary workaround to unblock the users, is to manually edit the filter permissions (as the filter owner) and share it with the appropriate user groups or projects.
However, this is not ideal, as Team-Managed projects are not expected to rely on filter permissions for board access.

For a permanent workaround, please reach out to Atlassian Support