import contacts dialog is misleading
Maintainers usually reply within 4 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 72/100
Research direction
The wording comes from the app's string resources, so search the Kotlin/Android project for the Import contacts title and the target contact source label used in the address-book picker dialog. Check whether the translated string files need the same change or only the English default. Done when the dialog title and field label read as a destination (for example, choosing where to import) rather than a source.
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 bug report will be dismissed otherwise.
- This issue contains only one feature request.
- I have read and understood the contribution guidelines.
- I optionally donated to support the Fossify mission.
Feature description
Hi,
If you import contacts on Fossify Contacts
- Settings
- Import contacts from vcf
- select the file to import
Now a dialog appears to select in which address book you want the contacts to be imported.
It states:
title: Import contacts
field's title: target contact source
But source means where something comes from, the origin, and not the destination. So it seems that it is asking where the contact was.
Isn't it misleading?
possible solution
Title: import contacts to
Field's title: select / choose address book
Why do you want this feature?
Dialog should be more clear
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
-
New field: IBANOpenfeature request needs triage
Difficulty 4/5 3-5 days Newbie friendliness 48/100
FossifyOrg/Contacts#613 ·
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
All issues in FossifyOrg/Contacts
Similar issues
-
afk-ok area:data-quality importer size:S
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
enorm-labs/event-junkie#3301 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
rustyrazorblade/easy-db-lab#1017 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
callstack/react-native-brownfield#492 · 1 comment ·
Maintainers usually reply within 4 days