Update support API todo progress
This commit is contained in:
Submodule HarborForge.Backend updated: 43af5b29f6...96cbe109ec
@@ -205,7 +205,7 @@
|
|||||||
- [x] Ensure `milestone-code` is accepted in get/update/delete/progress APIs
|
- [x] Ensure `milestone-code` is accepted in get/update/delete/progress APIs
|
||||||
- [x] Ensure `task-code` is accepted in get/update/delete/transition APIs
|
- [x] Ensure `task-code` is accepted in get/update/delete/transition APIs
|
||||||
- [ ] Ensure `meeting-code` is accepted in get/update/delete/attend APIs
|
- [ ] Ensure `meeting-code` is accepted in get/update/delete/attend APIs
|
||||||
- [ ] Ensure `support-code` is accepted in get/update/delete/take/transition APIs
|
- [x] Ensure `support-code` is accepted in get/update/delete/take/transition APIs
|
||||||
- [x] Ensure `propose-code` is accepted in get/update/delete/accept/reject/reopen APIs
|
- [x] Ensure `propose-code` is accepted in get/update/delete/accept/reject/reopen APIs
|
||||||
- [x] Add code-based list filters where missing
|
- [x] Add code-based list filters where missing
|
||||||
- [x] Ensure CLI-related list payloads always include canonical code fields
|
- [x] Ensure CLI-related list payloads always include canonical code fields
|
||||||
@@ -228,7 +228,7 @@
|
|||||||
- [x] Add/confirm conflict behavior when task already has a different assignee
|
- [x] Add/confirm conflict behavior when task already has a different assignee
|
||||||
- [ ] Add/confirm backend route for meeting attendance (`meeting attend`)
|
- [ ] Add/confirm backend route for meeting attendance (`meeting attend`)
|
||||||
- [ ] Ensure meeting attendance updates participant list
|
- [ ] Ensure meeting attendance updates participant list
|
||||||
- [ ] Add/confirm backend route for support self-assignment (`support take`)
|
- [x] Add/confirm backend route for support self-assignment (`support take`)
|
||||||
|
|
||||||
### 2.5 Frontend-facing code migration support
|
### 2.5 Frontend-facing code migration support
|
||||||
- [ ] Add code-based detail endpoints or code query support for frontend routing
|
- [ ] Add code-based detail endpoints or code query support for frontend routing
|
||||||
|
|||||||
Reference in New Issue
Block a user