Allow creating spaces in admin settings

[butonic]

Currently, spaces can be disabled and deleted in two ways:

1. via the files app
2. via the admin settings (batch mode)

New spaces can only be created in the files app.

What is the rationale behind this? Why do we have two places ways to do the same thing? Why can we not create spaces in the admin settings?

Can we merge the batch management into the files app? Or should we add support for creating spaces to the admin settings as well?

In the future I think admins may want to decide which storage provider should host a new space ... but even that might be possible to do in the files app...

[AlexAndBear]

Spawning @tbsbdr and @kulmann

[kulmann]

Because we only had time for the most important feature set back then. I don't see a reason forbidding creating spaces in the admin settings app. Actually on the contrary, it makes perfect sense. We just never thought about it anymore when the MVP was done.

Happy to have it. Files app should always be the most simple version of the process. Having more complexity in the admin settings app is fine.

[AlexAndBear]

Description

Creates space via admin settings

User Stories

As an admin I want to create spaces in the user settings, same as in the files app

Value

Easy management of spaces

Acceptance Criteria

• We have a button New Space in Admin settings -> Spaces

• Button opens New Space modal

• User can enter a new name for the space

• Created space should appear in the spaces list

• Reuse already existing component from the files app

Definition of ready

• Everybody needs to understand the value written in the user story
• Acceptance criteria have to be defined
• All dependencies of the user story need to be identified
• Feature should be seen from an end user perspective
• Story has to be estimated
• Story points need to be less than 20

Definition of done

• Functional requirements
  • Functionality described in the user story works
  • Acceptance criteria are fulfilled
• Quality
  • Code review happened
  • CI is green (that includes new and existing automated tests)
  • Critical code received unit tests by the developer
• Non-functional requirements
  • No sonar cloud issues
• e2e test