UXPROD-3456 - Getting issue details... STATUS
Problem(s):
- Not knowing what recent edit have been can made to organizations makes it difficult to troubleshoot issues
- Not having a complete history of Organization changes can mean sacrificing valuable information when a comment is changed etc.
Use Cases & Requirements:
| Requirement | Status | Use cases |
|---|---|---|
| User is shown what field was edited and when it was edited (Date and Time), in local timezone | PENDING | |
| User is shown what the original value was and what new value was input | PENDING | |
| User can filter through list of changes. Filtering on original value, new value or field name | PENDING | |
| User is able to enter a note or reference a note such that it can be seen in the "change log" | PENDING | |
| Changes tracking begins after Organization has been opened for the first time | PENDING | |
| User can reveal what fields have been edited, if needed. | PENDING | |
| Track changes made by system users. Track updates made by the Organization to related records. Ie. pieces or encumbrances created or deleted. | 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-3457 - Getting issue details... STATUS