The same counter form added to different projects in Collect, share chosen values in the counter form
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
Research direction
Start by reproducing the behavior using the counter.xlsx form from counter.xlsx.txt across two projects in ODK Collect, following the listed steps on Android. The expected sharing or isolation behavior is not decided in the issue, so first establish that requirement; done means the same-form values follow the agreed project-scoping behavior.
Written by the indexing model from the issue text.
Description
Counter version
ODK counter v1.0.0, master version 6284d53f53a21af047dee19afbb51e58d6e505ab
Android version
10, 13
Device used
Redmi 9T, Pixel 6a
Problem description
If there are different projects in Collect using the same counter form (with counter app installed), after filling answers in one project the answers are also present in other projects using the same form.
Steps to reproduce the problem
- Add counter.xlsx form to two different project in Central.
counter.xlsx.txt - Add those projects (with access to the form) to Collect.
- Go to the first project in Collect and fill in the counter form (e.g change values to 2).
- Go to the second project in Collect and check the answers (by tapping Launch) in the counter form.
In the second project the user sees the values from the first project.
Expected behavior
I’m not sure if the same form in all projects (on one device) should share values in the counter form.
- Dominant language
- Kotlin
- Stars
- 5
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a 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 getodk/counter
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
nightscout/AndroidAPS#5621 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
confluentinc/intellij#683 ·
Maintainers usually reply within 9 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
theopenconversationkit/tock#2166 ·
Maintainers usually reply within 1 day
-
follow-up
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
navikt/innsending-api#531 ·
Maintainers usually reply within 2 days
-
bug CLI
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
rafaeltonholo/svg-to-compose#379 ·