You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
Description
User Stories
Value
Acceptance Criteria
Note:
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: