"Link Entity List abc.geojson" button in drafts

Open
#2,333 2 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
56/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
javascript
Domain
frontend

Research direction

Start by comparing how draft attachments and entity list files are identified in the project’s form draft and entity list pages linked in the report. Reproduce the case where both have the same name, then trace the code that decides whether to show “Link Entity List...” beside an attachment. Done means the button appears only for an attachment that can correctly be linked to the entity list.

Written by the indexing model from the issue text.

Description

frontend needs testing
Problem description

In drafts the button "Link Entity List..." appears next to a wrong file. It appears in attachments if in the project there's a entity list with the same name as the attachment/file.

URL of the page

https://test.getodk.cloud/projects/679/entity-lists
https://test.getodk.cloud/projects/679/forms/all-question-types/draft
https://staging.getodk.cloud/projects/56/forms/all-question-types/draft

Steps to reproduce the problem
  1. Publish an entity form with an entity list "abc".
  2. Create a draft of a non-entity form which requires an attachment "abc".
  3. Check if there's a button to link entity list
Screenshot
linkGeojsonEnt linkEntitiesGeojson
Expected behavior
Central version shown in version.txt

https://test.getodk.cloud/
versions:
7d6de621955c5bb6a68e098ca10c9cbb92285cdf (v2026.3.1)
0000000000000000000000000000000000000000 client (v2026.3.1)
de0d2a07fd7c9ff698cbc312e550dd40ff058340 server (v2026.3.1)
https://staging.getodk.cloud/
versions:
8ab600ac42902813df06547a85eb78d2800d9a47 (v2026.3.1-20-g8ab600a)
e512cd484f68009bbda4dc8696aff42f2be57b71 client (v2026.3.0-79-ge512cd484)
f5737ac0e07935c4f9a55c8660bc9fc40aeed231 server (v2026.3.0-32-gf5737ac0)

Browser

Chrome and Firefox

Dominant language
JavaScript
Stars
233
Forks
241
Avg merge
1d 22h
Merged PRs (30d)
13

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

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/central

All issues in getodk/central

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.