# Open Point DREAM-944 - Decide the counting model for row positions in expanded relation and children columns

Project: Stream Design System
Status: needs clarification
URL: https://community.openproject.org/work_packages/DREAM-944

## Details

| Attribute | Value |
| --- | --- |
| Involved people | Behrokh Satarnejad, Henriette Darge, Jens Ulferts, Darren Cadwallader |
| Assignee | Behrokh Satarnejad |
| Decision |  |
| Date |  |
| Module |  |
| Labels |  |

## Related to

| ID | Subject | Type | Status | Assignee | Project |
| --- | --- | --- | --- | --- | --- |
| DREAM-860 | Decide grid or treegrid semantics for the work package table | Open Point | needs clarification | Behrokh Satarnejad | Stream Design System |
| DREAM-938 | Accessible row positions and counts in the work package table | Implementation | closed |  | Stream Design System |
| DREAM-941 | Row-position metadata for hierarchy work package tables | Implementation | rejected |  | Stream Design System |

## Description

### Decision needed

<mention class="mention" data-id="DREAM-942" data-type="work_package" data-text="#DREAM-942">#DREAM-942</mention> cannot start until the team decides how accessible row positions (`aria-rowindex` / `aria-rowcount`) are counted while a relation or children column is expanded. Relation occurrences and repeated occurrences of one work package under several owners are not described by the query results, and how many of them precede a page depends on which relation columns the request names and which owners are expanded. Expansion state is client-side and session-wide (`wp-view-relation-columns.service.ts`).

### Options

1.  **The server counts every occurrence for the named relation columns, regardless of expansion.** Positions exist whether or not an owner is expanded; collapsed owners keep their slots (stable gaps, as decided for groups and hierarchies on 2026-10-24). Stateless API, positions never shift on expand or collapse, consistent with the shipped model. Cost: a relation count per named column over the whole query on every collection request, and `aria-rowcount` includes rows that may never be rendered.
2.  **The request carries the expansion state; the server counts only expanded occurrences.** Counts match what the user can reach and the query stays cheap. Cost: every expand or collapse changes every later position and needs a refetch or a client-side recount; cross-page consistency depends on sending the same state with every page; the state leaks into URLs or request bodies.
3.  **Keep withdrawing positions while a relation or children column is expanded (today's behaviour) and ship 18.0 without <mention class="mention" data-id="DREAM-942" data-type="work_package" data-text="#DREAM-942">#DREAM-942</mention>.** No fabrication; an acceptance-criteria exception that needs recorded NVDA/VoiceOver results and feature-owner acceptance before it is chosen for 18.0; nothing to build before the 2026-11-11 feature freeze. Cost: assistive-technology users lose positions and counts whenever they expand a relation column; must be recorded as an accepted gap in <mention class="mention" data-id="DREAM-846" data-type="work_package" data-text="#DREAM-846">#DREAM-846</mention> and re-checked in <mention class="mention" data-id="DREAM-897" data-type="work_package" data-text="#DREAM-897">#DREAM-897</mention>.
4.  **Frontend-only when the page holds the complete result set** (count rendered occurrences, withdraw otherwise). Covers single-page queries only; a partial form of 1 or 2 rather than an alternative.

### Recommendation for discussion

Option 3 for 18.0, recorded explicitly. Decide between 1 and 2 after <mention class="mention" data-id="DREAM-897" data-type="work_package" data-text="#DREAM-897">#DREAM-897</mention> shows whether positions with expanded relation columns matter to screen-reader users. If they do, option 1 for consistency with stable gaps, provided the count query cost is acceptable on large queries.

**Update 2026-10-31:** <mention class="mention" data-id="DREAM-942" data-type="work_package" data-text="#DREAM-942">#DREAM-942</mention> moved to target version 18.1.0, sequenced after the <mention class="mention" data-id="DREAM-959" data-type="work_package" data-text="#DREAM-959">#DREAM-959</mention> refactorings. Unless the schedule changes, 18.0.0 ships with today's behaviour (positions withdrawn while a relation or children column is expanded), which is option 3 **proposed**, not chosen: choosing it still needs the recorded NVDA/VoiceOver results from <mention class="mention" data-id="DREAM-897" data-type="work_package" data-text="#DREAM-897">#DREAM-897</mention> and feature-owner acceptance named above. <mention class="mention" data-id="DREAM-846" data-type="work_package" data-text="#DREAM-846">#DREAM-846</mention> lists it under "Proposed accepted gaps". The counting model for 18.1.0 (option 1 or 2) also remains to be decided here.

**Update 2026-11-09:** moved with <mention class="mention" data-id="DREAM-942" data-type="work_package" data-text="#DREAM-942">#DREAM-942</mention> and <mention class="mention" data-id="DREAM-943" data-type="work_package" data-text="#DREAM-943">#DREAM-943</mention> to the follow-up feature <mention class="mention" data-id="DREAM-996" data-type="work_package" data-text="#DREAM-996">#DREAM-996</mention>, target version 18.1.0. This Open Point decides the 18.1.0 counting model (option 1 or 2). The 18.0.0 withdrawal (option 3) is accepted or rejected in <mention class="mention" data-id="DREAM-846" data-type="work_package" data-text="#DREAM-846">#DREAM-846</mention> under Proposed accepted gaps, on #DREAM-897's evidence.

### Resolution criteria

  - A recorded choice between options 1 and 2 for 18.1.0, with reasons.
  - For options 1 and 2: the occurrence key shape (owner, relation type, target) and how a work package repeated under two owners is numbered.
  - \#DREAM-942's scope item 1 replaced by a reference to this decision.
