Study View genes input allows OQL, but not OQL trackgroups

[pvannierop]

Background

On study view one can add OQL queries for analysis in results view. For instance this works:

TP53: HOMDEL
BRAF: V600E

This results in:

Problem

Entering track group OQL format in the study view does not work. For instance:

["My fav genes"  TP53: HOMDEL, BRAF: V600E]

This results in:

Reference

The correct representation of this query can be obtained when this query is entered on the query page:

[AdityaP700]

This issue looks interesting to me , if no one is working on this issue i would like to take the challenge . Thanks for anticipation

[tushar-2320]

hey @dippindots @inodb I would like to work on this issue?

[DhanrajRateria]

Hi everyone! 👋

I have investigated this bug and just opened a Pull Request to fix it over on the frontend repo: [Insert link to your Pull Request here]

What was happening:
The Study View was using a naïve string split on the gene query input. This meant that a valid track group like ["My fav genes" TP53: HOMDEL, BRAF: V600E] was being chopped in half at the internal comma, causing it to render as separate, broken tracks on the Results page rather than a single grouped track.

The Fix:
Instead of trying to patch the string split with Regex, I updated StudyViewPageStore.ts to utilize the existing robust AST parser (parseMergedTrackOQLQuery). I also implemented a new unparseOQLQuery function in oqlfilter.ts to properly serialize the parsed SingleGeneQuery | MergedGeneQuery objects back into a valid OQL string for the formOps submission.

I've also added unit tests to ensure OQL track groups are preserved perfectly. Looking forward to any feedback! (As a prospective GSoC 2026 applicant, I really enjoyed tracking this one down in the frontend monorepo).

---

cBioPortal/cbioportal-frontend#5450