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] Simple Import from oneDrive #9151

Closed
exalate-issue-sync bot opened this issue Jun 5, 2023 · 0 comments · Fixed by #9150
Closed

[web] Simple Import from oneDrive #9151

exalate-issue-sync bot opened this issue Jun 5, 2023 · 0 comments · Fixed by #9150
Labels

Comments

@exalate-issue-sync
Copy link

Description

User Stories

  • As a user I want to import a file from onedrive so that I can use solely ocis as my cloud storage.

Value

  • foundation to develop extension system

Acceptance Criteria

  • Scribble: https://whimsical.com/skyloader-sB7w29aT1KUGbKauknVU8@7YNFXnKbZAKvUABdpZceA
  • Add option "Import" to Upload button (Icon: file-cloud-fill)
  • click opens uppy dashboard modal
  • dashboard shows only oneDrive as selectable provider
  • click on onedrive icon shows next uppy dialog "Please authenticate with OneDrive to select files"
  • Click on "Connect to oneDrive" triggers authentication flow (all given by uppy/onedrive)
  • after successful authenication the user gets guided through the selection and upload flow, given by uppy
  • selected files are uploaded to the current folder
  • Note: no need to import folder structure (flat file structure ist okay for this first step)
  • the user needs to wait until the upload is finished (no extra error / resume handling etc.)

Note: Extra preparation is needed to set up developer tools like a reverse proxy to enable working with companion

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
  • 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