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

User Data Model #51

Closed
3 tasks done
brokkoli71 opened this issue Nov 14, 2022 · 3 comments
Closed
3 tasks done

User Data Model #51

brokkoli71 opened this issue Nov 14, 2022 · 3 comments
Labels
1 First Priority (highest) BP-HGHK BP Giese/Karl Project Backlog

Comments

@brokkoli71
Copy link
Collaborator

brokkoli71 commented Nov 14, 2022

User stories

As a developer I want a unified user data model in order to reduce confusion

Context:

Acceptance Criteria

  • able to store user login data
  • possibility of adding more user specific data
  • communicate with teams working on Dummy Items #29
@brokkoli71 brokkoli71 added the in preparation This issue has not been finalized, POs need to further specify this issue label Nov 14, 2022
@brokkoli71 brokkoli71 mentioned this issue Nov 14, 2022
5 tasks
@brokkoli71 brokkoli71 added Project Backlog 1 First Priority (highest) BP-HGHK BP Giese/Karl BP-BR BP Renard and removed in preparation This issue has not been finalized, POs need to further specify this issue labels Nov 14, 2022
@rebekka0111 rebekka0111 mentioned this issue Nov 15, 2022
6 tasks
@benn02 benn02 added the Clarification needed Issue needs to be more specific label Nov 18, 2022
@benn02
Copy link
Collaborator

benn02 commented Nov 18, 2022

What does unified with item store mean? Is this story also about creating an item storage? If not that needs an extra Story if yes we need to update this one

@brokkoli71
Copy link
Collaborator Author

brokkoli71 commented Nov 21, 2022

@benn02
[edited acceptance criteria]

What does unified with item store mean? Is this story also about creating an item storage? If not that needs an extra Story if yes we need to update this one

it means you should talk with the people working on #29 on how to implement storage of data to make it consistent. If already implemented, you can mark this issue as done

@brokkoli71 brokkoli71 removed Clarification needed Issue needs to be more specific BP-BR BP Renard labels Nov 21, 2022
@benn02 benn02 mentioned this issue Nov 22, 2022
Closed
3 tasks
@dasGoogle
Copy link
Collaborator

We talked about this in the HGHK meeting and found that the acceptance criteria are already fulfilled by the skeleton prvoded by the teaching team.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1 First Priority (highest) BP-HGHK BP Giese/Karl Project Backlog
Projects
None yet
Development

No branches or pull requests

3 participants