UXPROD-3456 - Getting issue details... STATUS
Problem(s):
- Not knowing what recent edit have been can made to invoices makes it difficult to troubleshoot issue
- Not having a complete history of invoice changes can mean sacrificing valuable information for audit trails, etc.
Use Cases & Requirements:
| Requirement | Status | Use cases |
|---|---|---|
| (SAMPLE) User is shown what field was edited and when it was edited (Date and Time), in local timezone | PENDING | (SAMPLE) As an Invoice payer or approver, I need to be able to track the history of an invoice in the event there are any discrepancies between the library's records and the vendor's. |
PENDING | ||
PENDING | ||
PENDING | ||
PENDING | ||
PENDING | ||
PENDING |
Proposed workflow:
Access change log
See
Requirements Board:
Questions:
Question | Status | Conclusion | Comments |
|---|---|---|---|
OPEN |
Work Breakdown Structure:
Features:
UXPROD-204 - Getting issue details... STATUS
UXPROD-3456 - Getting issue details... STATUS