[DASHBOARD] Wrap/Unwrap Handling #725
Description
Overview
What?
Wraps and Unwraps currently display as Transfers
We should handle them in a separate tab
How?
Why?
Deadline:
UI/UX Design:
Acceptance criteria
- ...
- Satisfies entire acceptance criteria
- Consider communication & visibility
- Code review is approved by at least 2 reviewers
- Tested by Elvijs/QA & discovered bugs resolved
- Documentation updated
- Assignee/opened by merges PR
- Automated E2E tests for happy path
- Code is merged
- Observability of critical user path
- Steps to access code change as a user
Links/Resources
- ...
Readiness criteria
- Descriptive title
- What?
- Why?
- How?
- Acceptance criteria complying with Definition of Done
- Estimate/Story points
- Deadline: If not a part of an epic
- Priority: Reflected as order on the board, walking the board from the top and right
- Assignee
- Labels
- Link to epic: If belonging to an epic
- A task is always a separate ticket/issue
- UI/UX Design (optional)
- Blockers/Prerequisites (optional): Use Zenhub blocked by/blocking feature