Create apartment request ad

[fingeririna]

Story: As a user I want to post an ad for apartment request, in order to find a suitable apartment for me to rent.

I select:

• Category: Accomodation
• "I'm looking for"
• Type of accomodation: Apartment

I can fill in:

• Title*
• Location*
• Zipcode*
• Radius (km)
• Min Rooms
• Min Living space (m2)
• Max Rent
• Price unit* (per month, per week, per day)
• Furnished (yes, no)
• Temporary (yes, no)
• Available*
• dd.mm.yyyy
• Description* (brief description of accommodation, a size, floor I am looking for)
• Brief description about me*
• Phone number*
• E-mail*

See also UI field catalog in #132

Not part of this Story: Pictures upload

Acceptance criteria:

• [x] AC1: The user select Accomodation->"I'm looking for" ->Apartment and get all fields as above
• [x] AC2: The user can fill all the fields
• [x] AC3: Fields are validated against format and mandatory
• [x] AC4: The user can pablish apartment request ad

Tasks:

• [x] T1: Attach the required fields in the database to the subtype
• [x] T2: Check if the backend returns the correct fields
• [x] T3: Check if the fields are shown in the UI
• [x] T4: Check if the values are saved correctly

Depends on #137

---

DoD

• [x] Story is tested against acceptance criteria
• [x] Unit test should be passed
• [x] Integration test is done ( if applicable)
• [x] Non-functional requirements are met
• [x] Story ok-ed by Product Owner
• [x] Peer Code Review performed
• [x] Any configuration or build changes documented
• [x] any database changes are documented in Database

[ghost]

@fingeririna and @TimmyAeberli can we modify the story to exclude the picture upload? There's a separate story for that - #48 which is dev ready.

P.S. After talking with Timmy - I have removed the image upload part of the story.

[ghost]

Leaving this here in case Timmy doesn't find enough info about the granularity of filtering for the shown fields. From the title for me the shown fields should be based on:

• CATEGORY(accommodation or car sharing currently)
• TYPE(request of offer)

but in the description it's mentioned "request for accommodation room", which for me means that the fields are filtered based on

• CATEGORY(accommodation or car sharing currently)
• TYPE(request of offer)
• TYPE OF ACCOMODATION(room, apartment, house or parking space currently)

From the structure of the database I suppose it's only about CATEGORY and TYPE. If there's an additional required field check(TYPE OF ACCOMODATION) - this would need additional database changes and UI ones or hardcoding some things on the UI(which would be pretty ugly and inconsistent with the other filtering).

[TimmyAeberli]

@fingeririna @yordyo After investigating the tickets and our notes on previous refinements I must say:

• We intended dependencies to TYPE OF ACCOMODATION, because the fields for ROOM and APPARTMENT would be different. I suggest changing the DB but would like to check back with Irina upon her return on monday