New field: IBAN
Maintainers usually reply within 4 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Domain
- mobile, mobile-dev
Research direction
Start by tracing how existing contact fields are defined, stored, and shown or edited in the app. Check whether the contact data model and relevant UI support adding a field like IBAN, and identify the tests covering those paths. Done means IBAN can be saved to a contact and accessed in Fossify Contacts.
Written by the indexing model from the issue text.
Description
Checklist
- I made sure that there are no existing issues - open or closed - to which I could contribute my information.
- I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
- I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
- I have taken the time to fill in all the required details. I understand that the request will be dismissed otherwise.
- This issue contains only one feature request.
- I have read and understood the contribution guidelines.
Feature description
Add field for IBAN (bank number)
Why do you want this feature?
I save IBAN numbers in my Google Account, but can't access them from Fossify Contacts
Additional information
No response
- Dominant language
- Kotlin
- Stars
- 917
- Forks
- 73
- Avg merge
- 5d 8h
- Merged PRs (30d)
- 7
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from FossifyOrg/Contacts
-
bug needs triage
Difficulty 3/5 1-2 days Newbie friendliness 64/100
FossifyOrg/Contacts#618 ·
Maintainers usually reply within 4 days
-
feature request needs triage
Difficulty 3/5 1-2 days Newbie friendliness 65/100
FossifyOrg/Contacts#614 · 1 comment ·
Maintainers usually reply within 4 days
-
bug needs triage
Difficulty 4/5 3-5 days Newbie friendliness 52/100
FossifyOrg/Contacts#612 · 5 comments · 1 reaction ·
Maintainers usually reply within 4 days
-
bug needs triage
Difficulty 3/5 1-2 days Newbie friendliness 62/100
FossifyOrg/Contacts#608 ·
Maintainers usually reply within 4 days
-
feature request needs triage
Difficulty 4/5 3-5 days Newbie friendliness 48/100
FossifyOrg/Contacts#607 ·
Maintainers usually reply within 4 days
All issues in FossifyOrg/Contacts
Similar issues
-
enhancement
Difficulty 2/5 Under an hour Newbie friendliness 72/100
afarber/OpenMapView#22 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
nightscout/AndroidAPS#5245 ·
Maintainers usually reply within 1 day
-
Feature:Resolution
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
intellij-elixir/intellij-elixir#4396 ·
Maintainers usually reply within 1 day
-
s: need triage
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Tencent-TDS/KuiklyUI#1786 ·
Maintainers usually reply within 1 day
-
ExprQuerySet.getChildren() omits WITH clausePossibly taken A pull request linked to this issue is open or already merged. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
partiql/partiql-lang-kotlin#1972 ·