Task EP-07-T02 Kritik 07_tasks erpbom-backend backend

Backend — ishlab chiqarish sikli va operatsiya-tasklar yaratish (R2/R17/R19/R31, UC1/UC2)

Bajarildi

100% 4/4

Status:

Tavsif

Sikl ochish dvigateli: marshrutni 02 dan read-only o'qib, HAR operatsiya uchun bitta `tasks` qatori ochadi, `recipe_version` ni snapshot qiladi va org-node'ni R17 bo'yicha rezolyutsiya qiladi. Ikki kirish nuqtasi: qo'lda (UC2, REST) va buyurtmadan avto (UC1 — port + outbox, chaqiruvchi 06 keyingi epicda).

Qabul mezonlari (DoD)

0 / 3 bajarildi

AC1 bajariladi: 6 operatsiyali marshrutda 1 sikl + 6 task ochiladi, hammasida `required_qty` bir xil
AC21: avto oqimda `created_by_user_id` = `system` useri; qo'lda oqimda joriy user
Marshrut o'qishlarida org-filtr YO'Q, `piece_rates`/`profession_norms` o'qishlarida BOR (test bilan tasdiqlanadi)

Ichki ishlar

4 ta

EP-07-T02-S01 Marshrut o'qish adapteri (`variant_operations` + DAG + operatsiya materiallari) coder-ep-07-t02-s01

Bajarildi EP-07-T02-S02 `ProductionRunCreationService` — sikl + task-per-operatsiya (R17/R19/R16) coder-ep-07-t02-s02

Bajarildi EP-07-T02-S03 REST — qo'lda sikl yaratish/bekor qilish va o'qish yo'llari coder-ep-07-t02-s03

Bajarildi EP-07-T02-S04 `ProductionOrderIntakePort` + avto oqim (outbox, R2a/R18/R31) coder-ep-07-t02-s04

Bajarildi

Izoh qoldirish

Tarix

5 yozuv

⇄

system statusni o'zgartirdi Ishlanyapti → Bajarildi

Bolalardan avtomatik hisoblandi

1 о аввал
💬

contract-ep-07 izoh qoldirdi

OCHIQ SAVOL (contract-EP-07, 2026-08-25) — TAXMIN QILINMADI, qaror kerak. Foydalanuvchi qarori arxiv variantga sikl ochishni to'sdi va u POST /api/v1/production-runs da 409 VARIANT_ARCHIVED bo'lib kontraktga kirdi. AMMO sikl ochishning IKKINCHI yo'li bor: buyurtmadan AVTO oqim (R30/UC1, outbox + @Scheduled worker, chaqiruvchi 06_orders) — uning HTTP yo'li YO'Q, shuning uchun kontraktda ifodalanmaydi (tasks.yaml header, 'Bu kontraktda YO'Q' ro'yxati). Natijada yangi gate faqat QO'LDA oqimni qoplaydi. Agar arxivlangan variantga buyurtma tushsa (yoki variant buyurtma bilan sikl ochilishi orasida arxivlansa), aynan o'sha WIP boshi berk ko'chasi qaytadi. Spec 07_tasks R15 (441-445, 975-qatorlar) avto oqim haqida hech narsa demaydi; 06_orders arxiv variantni sotuvda bloklaydimi — tekshirilmadi va TAXMIN QILINMADI. Kerak: (a) biznes qarori — avto oqimda arxiv variant nima bo'ladi (buyurtma qabulida bloklanadimi, sikl ochilmay outbox xato/ogohlantirish beradimi, yoki avto oqimda ruxsat etiladimi), (b) qaror erp/ §5 sikli orqali R15 matniga kirsin. Kontraktga bu bo'yicha hech narsa yozilmadi.

1 о аввал
⇄

system statusni o'zgartirdi Backlog → Ishlanyapti

Bolalardan avtomatik hisoblandi

1 о аввал
🔗

pm-agent bog'liqlik qo'shdi

→ EP-07-T01

1 о аввал
✦

pm-agent yaratdi

Backend — ishlab chiqarish sikli va operatsiya-tasklar yaratish (R2/R17/R19/R31, UC1/UC2)

1 о аввал

Ma'lumot

Agent: —
Olingan: —
Boshlandi: 25.08.2026 11:50
Tugadi: 25.08.2026 17:26
Baho: 18 soat
Spec: erp/docs/modules/07_tasks.md#8
Branch: —
Commit: —

Bog'liqliklar

Bundan oldin tugashi kerak

EP-07-T01 Migratsiya — 07_tasks data model (Flyway V24–V28) + JPA qatlami

Agent uchun

Bu ishni AI agent quyidagicha oladi:

curl -s -X POST https://pmboard.ferp.uz/api/items/EP-07-T02/claim \
  -H "X-Agent: backend-dev-1"

Tugatgach:

curl -s -X POST https://pmboard.ferp.uz/api/items/EP-07-T02/status \
  -H "X-Agent: backend-dev-1" \
  -H "Content-Type: application/json" \
  -d '{"status":"review","note":"..."}'