G1 · Collection and Folder Structure: A Postman Collection is a **test folder** holding all requests written for `/api/v1/bugs` — but it only makes sense when grouped not by endp
A Postman Collection is a **test folder** holding all requests written for `/api/v1/bugs` — but it only makes sense when grouped not by endpoint, but by a real usage FLOW ("Bug Creation Flow", "Bug Lifecycle"). The closest Java equivalent is splitting packages under `src/test/java` by feature (`bugcreation`, `buglifecycle`), not by technical layer. **For a deep Collection/folder architecture guide → see the `/postman` page; here we are just carrying the Bug Tracker into Postman.**
🎬 Carrying the Bug Tracker into Postman
Bug Tracker Collection
We now carry the 6 endpoints (`/api/v1/bugs`) we built in GROUP B-D into Postman.
We group them not as an endpoint list, but as a real flow: create first, then manage the lifecycle.
The result: a flow-based Collection, readable at a glance.
From Endpoints to a Collection
Review the 6 endpoints of /api/v1/bugs (GROUP B-D).
Group by real usage flows like "creation", "lifecycle" instead of by endpoint.
Each flow is a folder, each request an item under it.
Order the steps for setting up a Postman collection by flow.