The same counter form added to different projects in Collect, share chosen values in the counter form

Open
#23 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
android, kotlin
Domain
mobile

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
  1. Add counter.xlsx form to two different project in Central.
    counter.xlsx.txt
  2. Add those projects (with access to the form) to Collect.
  3. Go to the first project in Collect and fill in the counter form (e.g change values to 2).
  4. 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

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from getodk/counter

All issues in getodk/counter

Similar issues

More Kotlin issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.