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

Show user details in right sidebar #6675

Closed
exalate-issue-sync bot opened this issue Mar 28, 2022 · 0 comments · Fixed by #6724
Closed

Show user details in right sidebar #6675

exalate-issue-sync bot opened this issue Mar 28, 2022 · 0 comments · Fixed by #6724

Comments

@exalate-issue-sync
Copy link

Description

User Stories

  • As an admin I want to view detailed information of a user so that I lookup account details.

Value

  • groundwork right sidebar / MVP

Acceptance Criteria

  • switch to toggle right sidebar

  • checkboxes for selction model, users can be selected

  • multiselect details panel: if multiple users are selected, right sidebar shows "xx users selected" (batch actions are not part of this story)

  • Quickaction "Details" opens the details panel

  • right sidbebar shows info of single selected user:

    • Headline "Details"
    • Avatar Image (or initials) + username + First and last name
  • Sidebar can be closed via "X"

  • only filled out tabular data are shown

  • if a section has no data, the section doesnt get shown

Not part of this story: abstraction of right sidebar

Tabular Data:

(https://github.com/owncloud/libre-graph-api/blob/da64814b52f4083787a942b333b95291aa0dd703/api/openapi-spec/v0.0.yaml#L738)

Tabular Data:

profile

  • displayName (text form field)
  • givenName (text form field)
  • surname (text form field)
  • Email (valid email format)
  • Role (dropdown, single select)
  • Status (dropdown, single select)
  • Quota if available (same as for spaces quota)
  • (userPrincipalName - what is this?)

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
    [ ] 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
@kulmann kulmann added this to To do in Web Sprint 17 via automation Mar 28, 2022
@pascalwengerter pascalwengerter moved this from To do to In progress in Web Sprint 17 Apr 1, 2022
@settings settings bot removed the p3-medium label Apr 6, 2022
@settings settings bot removed the p3-medium label Apr 8, 2022
Web Sprint 17 automation moved this from In progress to Done Apr 12, 2022
@kulmann kulmann added this to To do in Web Sprint 18 via automation Apr 25, 2022
@kulmann kulmann moved this from To do to Done in Web Sprint 18 Apr 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type:Story User Story
Projects
No open projects
Development

Successfully merging a pull request may close this issue.

0 participants