GET and PUT /api/settings in modules/governance hold the default owner, the escalation path and the approval deadline, and nothing in the dashboard reads or writes them. A person counts as an approver only through authority, being the default owner or being on the escalation path. So after #2072, which requires a signed-in approver to answer from the dashboard, an operator can make someone an approver in the dashboard only by giving them authority on the People page.
Done when: the default owner, the escalation path (people and per-step deadlines) and the approval deadline are editable in the dashboard, picking people from the People list, and a change takes effect on the next approval request.
`GET` and `PUT /api/settings` in modules/governance hold the default owner, the escalation path and the approval deadline, and nothing in the dashboard reads or writes them. A person counts as an approver only through authority, being the default owner or being on the escalation path. So after #2072, which requires a signed-in approver to answer from the dashboard, an operator can make someone an approver in the dashboard only by giving them authority on the People page.
Done when: the default owner, the escalation path (people and per-step deadlines) and the approval deadline are editable in the dashboard, picking people from the People list, and a change takes effect on the next approval request.
sam
added the highbug labels 2026-11-21 10:38:06 +00:00
Rescoped by #2095: default owner and escalation steps will name accounts (members), not people records, so the picker built here chooses from the org's members.
Rescoped by #2095: default owner and escalation steps will name accounts (members), not people records, so the picker built here chooses from the org's members.
#2095 is merged locally: default owner and escalation steps now take member account ids, validated as members, and the old person ids were mapped or cleared by migration 00049. What remains here is the dashboard picker.
#2095 is merged locally: default owner and escalation steps now take member account ids, validated as members, and the old person ids were mapped or cleared by migration 00049. What remains here is the dashboard picker.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
GETandPUT /api/settingsin modules/governance hold the default owner, the escalation path and the approval deadline, and nothing in the dashboard reads or writes them. A person counts as an approver only through authority, being the default owner or being on the escalation path. So after #2072, which requires a signed-in approver to answer from the dashboard, an operator can make someone an approver in the dashboard only by giving them authority on the People page.Done when: the default owner, the escalation path (people and per-step deadlines) and the approval deadline are editable in the dashboard, picking people from the People list, and a change takes effect on the next approval request.
Rescoped by #2095: default owner and escalation steps will name accounts (members), not people records, so the picker built here chooses from the org's members.
#2095 is merged locally: default owner and escalation steps now take member account ids, validated as members, and the old person ids were mapped or cleared by migration 00049. What remains here is the dashboard picker.