rdmorganiser / rdmorganiser/rdmo
Question-level “Reuse answer” dropdown shows incorrect tab label for merged collection values
@jochenklar is already working on this.
Since Aug 14, 2026.
- Dominant language
- Python
- Stars
- 133
- Forks
- 60
- Avg merge
- 3d 14h
- Merged PRs (30d)
- 21
Description
Description / Beschreibung
When reusing values at the individual question level for a collection question, the dropdown can show the wrong tab label for the selected source. The values themselves are loaded from different tabs correctly, but the dropdown displays them as if they all came from the first tab, e.g. Tab d1 instead of d1, d2, and d3 respectively.
This does not seem to affect whole-tab reuse, where the tab label is shown correctly.
Expected behaviour / Erwartetes Verhalten
The dropdown should show the correct source tab label for each reused value, or otherwise indicate clearly that the merged result contains values from multiple tabs.
It should not display all merged values as coming from the first tab if they actually come from different tabs.
Steps to reproduce / Schritte zum Reproduzieren
- Create or open a project with a collection page/tab structure, e.g. tabs d1, d2, and d3.
- Fill the same collection question in each tab with different values.
- Open another project/interview where the same collection question is available.
- Use the individual question-level Reuse answer action for that collection question.
- Search for and inspect the dropdown entries.
- Observe that the displayed tab label shows the first tab (for example Tab d1) even though the merged values actually come from d1, d2, and d3.
Context / Kontext
OS: macOS or Ubuntu
RDMO version: 2.5.1
Browser: Google Chrome
References / Verweise
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.
Assessment
This issue has not been assessed yet.