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] Display resource as disabled #9558

Closed
exalate-issue-sync bot opened this issue Aug 8, 2023 · 1 comment · Fixed by #9561
Closed

[Web] Display resource as disabled #9558

exalate-issue-sync bot opened this issue Aug 8, 2023 · 1 comment · Fixed by #9561
Assignees
Labels

Comments

@exalate-issue-sync
Copy link

exalate-issue-sync bot commented Aug 8, 2023

Description

User Stories

  • As a user I want to know if a file is in postprocessing state so that I know that its there but currently not accessible.

Value

  • visibility of system status
  • avoid user error

Acceptance Criteria

  • if a resource is not accessible but does exists on the system visualize it in a "disabled" state (c.f. disabled button)
    • Style: whole should get a "disabled" stlye eg: opacity: .6; filter:greyscale(1); cursor:wait;
    • Not part of the story: Loading-spinner, Tooltip and Colum rename to "Status" is not part of the story, should be done when we announce the postprocessing via sse.
  • the user can not conduct any fileaction or selection on it. user can solely see it
  • selection is not possible
  • accessibility needs to be taken into account (keyboard accessible)
  • keyboard navigation / selection skips the row
  • needs to be respected in tilesview
  • if query param for opened right sidebar is set, param gets igonred (has no effect)
  • if a resource which is currently in postprocessing state gets listed in seach results, click on this resource shows an error (needs to be fixed in another story / QA)
    Note:
  • there is an option in ocis to set the time for postprocessing for dev
  • this story is not to b e implemented via SSE - this is about the first step, SSE comes later

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
@exalate-issue-sync
Copy link
Author

Florian Schade commented: SSE part follows: owncloud/ocis#6992

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.

1 participant