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 creating and sharing a single file public link I want the link receiver to jump into editing/viewing the file content, so that they can collaborate without detours.
As a person receiving a single file public link I don't want to deal with the mental load of file metadata and deciding which editor to choose so that I can focus on the content that was shared with me.
Value
Access to content of a single file is as quick and easy to understand as possible.
Acceptance Criteria
Context: single file public link opens in a ResourceDetails view, which shows a preview image / file type icon and all available file actions (e.g. open in Preview app, Download, ...).
Open single file public link in default editor / application if one is available.
resolvePublicLink / resolvePrivateLink page adds new query param (e.g. openWithDefaultApp), ResourceDetails view redirect to default action if openWithDefaultApp is set and a default action is available.
Stay on the ResourceDetails view if no editors are available
Admin should be able to disable the public link resolving to the default editor (by default we want the routing to take place) via config.json options.
Add config option as environment variable to ocis (frontend service)
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. Minimum: check that routing is triggered.
[ ] 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
Access to content of a single file is as quick and easy to understand as possible.
Acceptance Criteria
Context: single file public link opens in a
ResourceDetails
view, which shows a preview image / file type icon and all available file actions (e.g. open inPreview
app,Download
, ...).resolvePublicLink
/resolvePrivateLink
page adds new query param (e.g.openWithDefaultApp
),ResourceDetails
view redirect to default action ifopenWithDefaultApp
is set and a default action is available.ResourceDetails
view if no editors are availableDefinition 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. Minimum: check that routing is triggered.
[ ] 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: