Appearance
Planning Workflow
Planning work in ProjectTrace follows this chain:
Project -> Epic -> Feature -> Requirement
Epics
Epics group related delivery work inside a project.
Create one when you want to organize a larger business outcome.
Steps:
- Open
Planning -> Epics. - Click
Create epic. - Choose the project.
- Enter a title, description, owner, and status.
Features
Features sit under epics and split the work into smaller deliverable chunks.
Steps:
- Open
Planning -> Features. - Click
Create feature. - Select the parent epic and project.
- Fill in the title, status, and owner.
Requirements
Requirements are the traceable statements you later connect to test cases and bugs.
Steps:
- Open
Planning -> Requirements. - Click
Create requirement. - Select the project and feature.
- Set the priority and status.
- Save.
Linking behavior
- A requirement can link to many test cases.
- A requirement can link to many bugs.
- The detail view shows the linked records and activity trail.
Practical rule
Keep the hierarchy consistent:
- Project owns the planning scope.
- Epic groups the outcome.
- Feature narrows the implementation.
- Requirement describes the behavior to validate.