## Summary When a user selects an answer to a Duo clarifying question, the options that were **not** chosen are currently hidden entirely once the thread resolves. This means the full context of what Duo considered — and what the user decided against — is lost from view. We already implemented a collapsed/toggle pattern for the case where **no** options are selected (resolved without an answer) in https://gitlab.com/gitlab-org/gitlab/-/merge_requests/253777 (merged). We should extend this same behavior to the case where a user **does** select an answer, showing the unchosen options in a collapsed state behind a toggle. This was raised in the [WS-7 Testing & Feedback thread](https://gitlab.com/groups/gitlab-org/-/work_items/22773#note_3934226554) by @nickbrandt: > I'd like to do exactly this. We implemented similar behavior in !253777 (when no options are selected), but I think we should also show a collapsed version of the options that weren't chosen for cases a user does select an answer. I mentioned this in the MR and also recently added it to the design, but failed to add a follow-up yet. The motivation is also tied to the decision log: when a resolved question is linked from the decision log, users navigating back to the originating thread should be able to see what options were on the table — not just the one that was chosen. This was discussed in the [WS-7 thread](https://gitlab.com/groups/gitlab-org/-/work_items/22773#note_3919650870) by @kushalpandya: > we'd be linking a resolved decision to the question thread, so if user wishes to see all the options, we can consider revealing back all the options even on a resolved thread (where today we hide all the options that weren't picked). ## Context ### Existing behavior (from !253777) The closed issue https://gitlab.com/gitlab-org/gitlab/-/work_items/617978 ("Collapse Duo clarifying-question options once the thread is resolved") implemented the following for the **no-answer-selected** case: - Options are collapsed by default behind a toggle (`Show suggested answers` / `Hide suggested answers`) - Options are rendered disabled (not interactive) once the thread is resolved - The custom answer input also renders disabled rather than being removed - The `Recommended` badge drops to `variant="neutral"` when disabled - The multi-select `Submit` button is hidden once the thread is settled ### What's missing For the **answer-selected** case, once a user picks one or more options and the thread resolves: - The chosen answer is shown (correct ✅) - The **unchosen options disappear entirely** (gap ❌) We should show the unchosen options in a collapsed state, consistent with the resolved-without-answer behavior, so users can always see the full set of options Duo considered. ### Design reference @nickbrandt has added this to the [Figma design](https://www.figma.com/design/uJb85wjoRaj7MMvjxAmdHf/SDD-Iteration-Path?node-id=46-30133&t=gnBPPNGPTsNS6WQ3-1) and also noted it in the [original MR review](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/253777#note_3811776428). ## Proposed behavior When a Duo clarifying-question thread is resolved **with** a selected answer: 1. The chosen answer(s) remain visible as they are today 2. The unchosen options are hidden by default, collapsed behind a toggle (e.g. `Show other options` / `Hide other options`) 3. When expanded, the unchosen options render in a disabled/greyed state (not interactive), consistent with the resolved-without-answer collapsed state from !253777 4. The toggle state is per-view only (resets on reload), same as the existing behavior ## Implementation notes - The existing `isDiscussionResolved` and `isAnswered` props on `ee/app/assets/javascripts/work_items/components/notes/duo_question_note.vue` can be combined to derive the new state: `isResolvedWithAnswer` = `isDiscussionResolved && isAnswered` - The existing `areOptionsVisible` / `showOptions` pattern from !253777 can be extended: for the answered case, only the **unchosen** options need to be collapsed; the chosen answer row stays visible - Disabled styling (`gl-bg-disabled gl-text-disabled`, `neutral` badge variant) already exists from !253777 and should apply to the collapsed unchosen options when expanded - The `DuoCustomAnswerInput` row behavior for this state should follow the design mock ## Acceptance criteria - [ ] A resolved question **with** a selected answer shows the chosen answer as today - [ ] The unchosen options are hidden by default behind a toggle - [ ] Expanding the toggle shows the unchosen options in a disabled/greyed, non-interactive state - [ ] The toggle state resets on page reload - [ ] A resolved question **without** a selected answer continues to behave as implemented in !253777 (no regression) - [ ] Jest specs cover: chosen-answer collapsed state, toggle expand/collapse, unchosen options non-interactive ## Related - https://gitlab.com/gitlab-org/gitlab/-/work_items/617978 — "Collapse Duo clarifying-question options once the thread is resolved" (closed, the no-answer case this builds on) - https://gitlab.com/gitlab-org/gitlab/-/merge_requests/253777 — the MR that implemented the no-answer collapse (merged) - https://gitlab.com/gitlab-org/gitlab/-/work_items/608859 — "Record a Decision when a Duo clarifying question is answered" - https://gitlab.com/groups/gitlab-org/-/work_items/22773 — WS-7: Testing & Feedback (source thread) - https://gitlab.com/groups/gitlab-org/-/work_items/22772 — WS-4: HITL & Notifications (parent epic)