Custom fields on issues: what do you actually need one for?

[imshashank]

Custom fields are the most requested thing Orbit deliberately does not have, and doing them badly makes every other surface worse: the filter engine is typed against known fields, analytics grouping is where the value is, MCP tools take names rather than ids, and a definition change has to fan out over realtime.

So before any design, this thread collects concrete needs. "I need a Severity field on bugs that I can group the board by" tells us more than a general request. Say what the field is, which team uses it, and where you need to see it (board, filters, analytics, an agent over MCP).

The previous issue (#128) is closed in favour of this thread; it reopens as an issue once there are enough real cases to design against.