Tighten issue picker action gating #181

New issue

Closed

opened 2026-04-12 19:29:29 +00:00 by barrettruth · 1 comment

barrettruth commented

2026-04-12 19:29:29 +00:00

Problem

The issue picker action surface is still implicit and list-state-driven instead of being explicitly validated per entry.

Right now the close/reopen action label is derived from the current list state, which is simple, but it does not establish a clear policy for mixed or stale data, future issue edit support, or forge-specific capability differences.

Expected

Define explicit per-entry issue action gating rules for the picker surface.

That should cover at least:

when Close is shown
when Reopen is shown
whether unavailable actions are hidden or disabled
how the picker refreshes after a state mutation
how future issue actions (such as edit) plug into the same policy

Notes

This is about picker-surface correctness and consistency, not issue semantic ops themselves.

## Problem The issue picker action surface is still implicit and list-state-driven instead of being explicitly validated per entry. Right now the close/reopen action label is derived from the current list state, which is simple, but it does not establish a clear policy for mixed or stale data, future issue edit support, or forge-specific capability differences. ## Expected Define explicit per-entry issue action gating rules for the picker surface. That should cover at least: - when `Close` is shown - when `Reopen` is shown - whether unavailable actions are hidden or disabled - how the picker refreshes after a state mutation - how future issue actions (such as edit) plug into the same policy ## Notes This is about picker-surface correctness and consistency, not issue semantic ops themselves.

barrettruth commented

2026-04-12 21:39:28 +00:00

Closing this because the product direction is to keep picker actions flat rather than introduce per-entry issue action gating. Any remaining issue-picker UX problems should be tracked as narrower feedback, refresh, or action-behavior bugs instead.