Closed akrguda closed 1 year ago
This is the database design for the changes. The changes are marked "yellow"
Please use the
in the ticket
Example or more information in https://github.com/AkrosAG/Akros-Marketplace/issues/159
Meeting with Asida, Anupama, Filipe, Timmy, Daniel
In the refinment meeting 15th november 2022 the team has decided to proof the use of keycloak in tihs case. For this proposition we create the ticket
https://github.com/AkrosAG/Akros-Marketplace/issues/218
to get the knowhow for using keycloak and the possibility to use keycloak in this ticket instead of the advertiser table.
After a technical review with @Filipe-Inacio there were several findings: the AD is already stored with keycloak and there is no need that the exact same AD is stored on a additional data base. @Filipe-Inacio will create a new ticket in order to remove the existing ADs from the system.
According @sereno77 I have creating following ticket: https://github.com/AkrosAG/Akros-Marketplace/issues/255
okayed by PO
As a user I want that my ad (topic) is stored related to my user login (advertiser) so that I can see just my ad for working on it with the ticket.
[x] Open Questions:
Is it possible to just have a n-to-n relationship between advertiser and topic? (Data Engineer -> Daniel) Answer: No, it's not necessary, as a user wants to be the only person to administer his ad (1 user, n topics)!
Implementation Suggestion:
DoR
Acceptance Criteria
DoD