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

✨ feat(component): Postcode form fields #811

Closed
1 task done
Feamusbal opened this issue Apr 27, 2023 · 1 comment
Closed
1 task done

✨ feat(component): Postcode form fields #811

Feamusbal opened this issue Apr 27, 2023 · 1 comment
Assignees
Labels
🎨 design UX expertice is required ✨ feature New feature or request 💬 ux & ds sync Topics for the weekly exchange between UX & DS Devs
Milestone

Comments

@Feamusbal
Copy link

Summary

The postal code form field is needed for most calculators as it is needed to know where customers live. Currently different teams are using different design approaches.

It is possible that a city has multiple postcodes (e.g., Basel has 4055, 4056, 4057 etc.) or that a postcode includes multiple villages (e.g., 1041 includes Dammartin, Montaubion-)Chardon, Naz, Poliez-le-Grand etc.)

The postcode form component should:

  • there be only one option for the postcode the city field shows the city name
    -there be multiple villages with the same postcode, users must choose the village and there is a hint in the field

-For bank now we are using the two field approach: https://acc-www.baloise.ch/banknow/car-search
Ban Now two fields

Use Case

Needed for any application which asks customers for their address in Switzerland, e.g., Ford standalone solution.

Preferred Solution

The postcode form component should:

  • there be only one option for the postcode the city field shows the city name
    -there be multiple villages with the same postcode, users must choose the village and there is a hint in the field

Additional Information

No response

Will this feature introduce breaking changes?

None

Code of Conduct

  • I agree to follow this project's Code of Conduct
@Feamusbal Feamusbal added the ✨ feature New feature or request label Apr 27, 2023
@Feamusbal Feamusbal changed the title ✨ feat(component): title Postcode form fields Apr 27, 2023
@Feamusbal Feamusbal changed the title Postcode form fields ✨ feat(component): Postcode form fields Apr 27, 2023
@hirsch88 hirsch88 added the 🎨 design UX expertice is required label Aug 8, 2023
@hirsch88 hirsch88 added this to the ✏️ Forms milestone Oct 12, 2023
@hirsch88 hirsch88 added the 💬 ux & ds sync Topics for the weekly exchange between UX & DS Devs label Dec 5, 2024
@hirsch88
Copy link
Member

hirsch88 commented Dec 5, 2024

We close this issue due to inactivity

@hirsch88 hirsch88 closed this as completed Dec 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🎨 design UX expertice is required ✨ feature New feature or request 💬 ux & ds sync Topics for the weekly exchange between UX & DS Devs
Projects
None yet
Development

No branches or pull requests

2 participants