[PO] Backlog priorisé et jalons datés #45
Labels
No labels
Compat/Breaking
EC01
EC02
EC03
EC04
EC05
EC06
Kind/BDD
Kind/Back
Kind/Bug
Kind/CICD
Kind/Cloud
Kind/Contenu
Kind/Data
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Front
Kind/IA
Kind/Infra
Kind/Monitoring
Kind/Security
Kind/Testing
Portée/Post-jury
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
ops/alerte
No milestone
No project
No assignees
1 participant
Notifications
Total time spent: 8 hours
Due date
florian
8 hours
No due date set.
Dependencies
No dependencies set
Reference
g2/enervision#45
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Exigence couverte
ENF-16
Épreuve servie
EC02 — Management
Charge estimée
1 j.h
Ce qu'on veut obtenir
Que chacun sache le matin quel ticket il prend, et que l'équipe sache à quelle date quoi doit être debout.
Critères d'acceptation
Comment on le vérifie
Tests aucun
Commande lecture du tableau des tickets, trié
Preuve capture du backlog ordonné et les trois jalons
Hors périmètre
Le découpage technique des tickets, qui appartient au Tech Lead.