Availability
Overview
It is possible to move a project to a single space only. The cross-space functionality provided by Birdview allows you to transfer a project from Space A to Space B. The conditions and outcomes of this operation are discussed below.
Please note that the project will be transferred along with all its activities, assignees, time entries, custom fields, etc.
During the process of importing into the destination space, Space A-specific custom fields and workflows change their scope from space-specific to global.
In this article
Permissions
To be able to move a project from Space A to Space B, the user needs to have the "Manage system settings" global permission and project management permissions in both spaces. These include the ability to add space members.
How to move projects between spaces?
It is possible to move projects between spaces in three ways:
- Using project batch operations in a space Activity center
- Using a project context menu when clicking on
- Using a project details sidebar
How will projects and activities be moved?
When moving projects between spaces, it's crucial to understand that the projects being moved will be completely removed from Space A. Along with the project, all its activities and time logs will also be transferred to Space B.
How will assignees be moved?
Users assigned to the projects and activities will be moved to Space B. However, it's important to note that they will still remain members of Space A. This approach ensures that members are not entirely removed from Space A, considering the possibility that they may have other projects and activities assigned to them in this space.
How will custom fields be moved?
When moving a project, Space A custom fields transition to a global scope, allowing their importation to Space B. Simultaneously, these custom fields become accessible for addition to other spaces, given their now-global scope. It's important to consider this aspect when moving projects between spaces.
How will workflows be moved?
The workflows follow the same logic as described for custom fields above. An in-use workflow in the project being moved, unless it is already global, becomes global in the process of moving. Consequently, it is imported to Space B and can be utilized in the project once the transfer is complete. Given its global scope, the workflow can now be used in other spaces as well. It's essential to keep this in mind when moving projects between spaces.