MerginMaps / MerginMaps/work-packages
New features from different teams should have filter-column automatically populated
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 11
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
New features from different teams should somehow have filter-column automatically populated with team values if emtpy, and that is not the case at the moment. If this doesn't work this way, after data sync you have records from all teams in each package.
tables:
- name: farms
method: filter-column
filter-column-name: survey_team
work-packages:
- name: TeamA
value: A
mergin-project: My Company/Survey Team A
- name: TeamB
value: B
mergin-project: My Company/Survey Team B
So if I'm on A team and if I add a new farm, shouldn't column "survey_team" be somehow populated with value "A"? If not immediately than on next work-package sync.
Contributor 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.
Research direction
Start by tracing the filter-column handling and work-package sync behavior described for survey.gpkg. Determine how a new farm record can receive the active team's value, then verify that syncing TeamA and TeamB packages keeps their records separated by survey_team.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, data
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100