Skip to content

[Mobile] Team administration: members, invites, statuses, automation, repositories - #34

Merged
wak327 merged 1 commit into
mobile-reportsfrom
mobile-team-admin
Sep 11, 2026
Merged

wak327 merged 1 commit into
mobile-reportsfrom
mobile-team-admin

Conversation

@wak327

@wak327 wak327 commented Sep 11, 2026

Copy link
Copy Markdown
Contributor

Closes #16 for everything the API exposes, with one deliberate exception noted below.

Rules render as English — "When an issue changes status and it is unassigned, assign it to Ada Lovelace." A rule is read far more often than it is written, usually to work out why an issue moved, and a grid of dropdowns does not answer that. Every lookup falls back by name, because a rule outlives the label it points at and a sentence with "undefined" in it is worse than one saying the label is gone.

Reordering statuses sends every id at once, as the API asks: two people dragging columns would otherwise interleave into an order neither chose. It uses arrows rather than a drag — the board already spends its drag on cards, and a second drag surface inside a sheet is both harder to hit and harder to verify without a device.

Deleting a status requires naming where its issues go, so the confirm offers the other columns rather than guessing.

A webhook secret is not put on screen until it is asked for; these screens get shown to other people.

What is not here

Rule authoring. A rule is a trigger plus six optional conditions plus seven optional actions — a form that belongs on a wider screen. Everything else about rules (reading, enabling, disabling, deleting, the run log) is here, and the panel says so and links out, as the issue allows for Jira import. Worth deciding whether that closes #16 or leaves a follow-up.

Another correction from checking: demoting the last admin is 409, not 400.

…sitories

Closes #16 for everything the API exposes, with one deliberate exception noted
below.

Rules render as English -- "When an issue changes status and it is unassigned,
assign it to Ada Lovelace." A rule is read far more often than it is written,
usually to work out why an issue moved, and a grid of dropdowns does not answer
that. Every lookup falls back by name, because a rule outlives the label it
points at and a sentence with "undefined" in it is worse than one saying the
label is gone.

Reordering statuses sends every id at once, as the API asks: two people dragging
columns would otherwise interleave into an order neither chose. It is driven by
arrows rather than a drag -- the board already spends its drag on cards, and a
second drag surface inside a sheet is both harder to hit and harder to verify.

Deleting a status requires naming where its issues go, so the confirm offers the
other columns rather than guessing. Guessing which column somebody's work lands
in is not a decision to make for them.

A webhook secret is not put on screen until it is asked for; these screens get
shown to other people.

Rule *authoring* is not here. A rule is a trigger plus six optional conditions
plus seven optional actions, which is a form that belongs on a wider screen --
everything else about rules (reading, enabling, disabling, deleting, the run
log) is. The panel says so and links out, as the issue allows for Jira import.

Another correction from checking: demoting the last admin is 409, not 400.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@wak327
wak327 merged commit 02c22ca into mobile-reports Sep 11, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant