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

Share List: Add inheritance-indicators #6528

Closed
tbsbdr opened this issue Mar 4, 2022 · 0 comments · Fixed by #6613
Closed

Share List: Add inheritance-indicators #6528

tbsbdr opened this issue Mar 4, 2022 · 0 comments · Fixed by #6613

Comments

@tbsbdr
Copy link
Contributor

tbsbdr commented Mar 4, 2022

Description

User Stories

  • As a user I want to see where I can change access permission of a folder and its siblings so that I'm in full control of it.

Value

  • data loss prevention
  • enable sharing in spaces

Acceptance Criteria

  • If the current folder or space is not the rights-giving folder, then a inheritance-indicator is displayed within the item
  • click on the indicator navigates to the inheritance giving folder
  • the inheritance indicator has the same look-and-feel like the "oc-resource-indicators"
  • tooltip of the inheritance indicator: "Navigate to inheriting folder"
  • the indicators are only displayed for shared folders, but not for spaces

Inheritance-Indicators: hover, default, truncated
Inheriting folder tag

known pattern:
image

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

is needed by "Make clear who else has access to a Space": #6283

Definition of done

  • Functional requirements
    [ ] functionality described in the user story works
    [ ] acceptance criteria are fulfilled
  • Quality
    [ ] codre 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
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant