Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Web] Create Space from resource(s) #8735

Closed
exalate-issue-sync bot opened this issue Mar 28, 2023 · 0 comments · Fixed by #8730
Closed

[Web] Create Space from resource(s) #8735

exalate-issue-sync bot opened this issue Mar 28, 2023 · 0 comments · Fixed by #8730
Labels

Comments

@exalate-issue-sync
Copy link

Description

User Stories

  • As as ownCloud we want that users get familiar with Spaces so that they enjoy the advantages of Spaces.

  • As a user I want to convert a folder from Personal to a Space so that I don't need to create, copy & paste everything manually.

Value

Acceptance Criteria

  • New file action (context menu) Create Space from selection; icon: layout-grid-line (note: unsure if this looks good, we might need to try out if another space-lookalike icon looks better)
  • Item is only available within Personal (not available within project Spaces) and if the logged in user has the permission to create spaces (Spaces, create-all)
  • Position of the context menu item: above "create or edit tags"
  • click on the item(s) opens a modal
    • Title: "Create Space from [foldername]" for single folder selection, "Create Space from selection" for other (file/folder) selection (also for single file)
    • Description: "Create a Space with the content of [foldername]. The content will be copied.", "Create a Space with the selected files. The content will be copied." for other selections.
    • Form: textfield like "Create Space" modal
    • Close modal on click of Create
  • Show progress bar while copy is in progress (i.e. make use of loadingService)
  • Show message "Space was created successfully" when the process is done

Definition of ready

[ ] everybody needs to understand the value written in the user story
[ ] acceptance criteria has to be defined
[ ] all dependencies of the user story need to be identified
[ ] feature should be seen from an end user perspective
[ ] user story has to be estimated
[ ] story points need to be less then 20

Definition of done

  • Functional requirements
    [ ] functionality described in the user story works
    [ ] acceptance criteria are fulfilled
  • Quality
    [ ] code review happened
    [ ] CI is green
    [ ] critical code received unit tests by the developer
    [ ] automated tests passed (if automated tests are not available, this test needs to be created and passed
    [ ] e2e tests: one for single folder selection, one for mixed file/folder selection.
  • Non-functional requirements
    [ ] no sonar cloud issues
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

0 participants