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

Edit profile data #6676

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

Edit profile data #6676

exalate-issue-sync bot opened this issue Mar 28, 2022 · 0 comments · Fixed by #6724
Labels
Type:Story User Story

Comments

@exalate-issue-sync
Copy link

Description

User Stories

  • As an admin I want to edit profiledata so that I can adminstrate accounts.

Value

  • usermangement

Acceptance Criteria

  • Quickation "Edit profile" opens subpanel "Edit profile"

  • In edit profile all tabular data except group assignments can be edited.

  • formfields can only be saved after succesfull validation

  • sticky bottom bar, refects to the admin, if changes where made:

  • If no changes where made:

    • Text: "No changes"
    • "Revert" button is disabled
    • "Save" button is inactive.
  • If changes where made:

    • Text "Unsaved changes"
    • "Revert" button -> click: dismisses unsaved changes;
    • "Save" button is active -> click, saves changes and shows toast "Changes were saved successfully"; doesnt leave the edit panel. ideal: change the bottom bar to reflect the user, that his changes took effect

to be defined: can quota be edited in the user management?

Tabular Data:

profile

  • displayName (text form field)
  • givenName (text form field)
  • surname (text form field)
  • Email (valid email format)
  • Password field (type: password; Masked with ⚫️⚫️⚫️⚫️⚫️)
  • 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type:Story User Story
Projects
None yet
Development

Successfully merging a pull request may close this issue.

0 participants