-
Notifications
You must be signed in to change notification settings - Fork 159
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
Clean urls and spaces mock #9308
Comments
@diocas @elizavetaRa
|
waiting for cern backend:
|
Status on 26th of October: waiting for graph api implementation to be able to proceed here. |
Basically the same requirements as here: #9379 (comment) Project title obviously also needs to be provided as drive name. |
Closing here since this is finished on our side. @elizavetaRa @diocas please feel free to create a new issue if you run into any trouble. |
Description
@elizavetaRa @diocas
lets please clarify in this ticket whats happening in Clean urls and spaces mock
(Create Project reuqirement is described here: Create EOS Projects on request)
User Stories
Value
Acceptance Criteria
Spaces
toProjects
basename(this.$route.params.driveAliasAndItem)
/trash/eos
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
[ ] functionality described in the user story works
[ ] acceptance criteria are fulfilled
[ ] 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
[ ] no sonar cloud issues
The text was updated successfully, but these errors were encountered: