Hi Digital.ai,
The Deploy GUI supports drag and drop functionality of directories. Release does not support this functionality for folders.
For example, in Deploy, when a directory A in Applications is dragged and dropped upon another directory B, it will be moved into B and will be a subdirectory of B.
Could this functionality also be built in Release for folders? This functionality is provided by the Release REST API but it would be more convenient when the GUI supports this.
Kind regards,
Ruud Muilwijk
by: Ruud M. | about a year ago | User interface
Comments
Ruud thank you for the request.
We will be evaluating this request with engineering team. We know that there are multiple dependencies for folders such as triggers active releases running, pending releases to start, and we would have to handle those when moving the folder. Once we have some initial investigation completed, I would like to join in a call discussing how would you see this handled, and if it's also the case in your setup.
Definitely need this. We've got scores of folders, and we're about to lose several days of our lives, moving folders, re-creating connections, re-creating patterns, re-creating team and folder permissions etc.
Enabling the movement of folders for directory reorganization in Release is frequently asked by our users. This is an important feature we need.
I have some comments concerning adding this feature to the GUI as well as the current restrictions available for Release Folder Moving.
1. Will restrictions remain the same when this is added in the GUI? Current known restrictions for the Move Folder API:
-- No releases currently running
-- No active triggers
-- No connections defined at Folder level.
--- This one would be nice if the Folder Connections could be moved as well.
2. When a Folder is moved, the completed and archived Releases retain their association to the owning folder, correct?
-- I am assuming these Releases will still be associated to the same Folder after it is moved and has a new parent.
3. For Folder moves, do permissions need to be re-applied?
Thank you for the valuable feedback and insights. We'll be dedicating our efforts to exploring potential solutions within the 24.3 (Fuji) timeframe. We'll then share our findings with the Digital.ai Community and may also conduct additional discovery interviews for further insights on the proposal.