| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
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 when a comment is changed etcInvoices in FOLIO can go through multiple iterations as they go through the entry and approval process. Libraries need the ability to track invoice changes for auditing and troubleshooting purposes.
- Invoice lines can also go through multiple iterations and updates. Libraries need the ability to track changes in individual invoice lines.
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 |
| During invoice update, approval, payment and audit, users may need to track changes made to the invoice over time. This information may include changes to price, currency, exchange rate and other invoice line item specifics, such as fund allocation changes. | ||||||
| User is shown what the original value was and what new value was input |
| When information changes, the original information is lost, and users may need to retain that original historical information. For instance, a user may need to refer back to an original planned fund allocation when the current allocation is different. | ||||||
| User can filter through list of changes. Filtering on original value, new value or field name |
| Over time, the number of changes can make it difficult to locate specific changes so the knowledge is effectively lost even though it is tracked in the system. | ||||||
| User is able to enter a note or reference a note such that it can be seen in the "change log" |
| In certain circumstances, it may be important to document why a particular change was made, and this needs to be captured somewhere. For instance, a user may wish to make a note that a fund allocation was changed on a particular invoice to account for insufficient available balances in a given fund or other similar circumstances. | ||||||
| Changes tracking begins after order has been opened for the first time |
| Changes are only a concern after the invoice has been opened for the first time. | ||||||
| User can reveal what fields have been edited, if needed. |
| In some systems, certain fields are highlighted when changed. This is sometimes used to highlight fields not normally subject to change. | ||||||
| Track changes made by system users. Track updates made by the order invoice to related records. Ie. pieces or encumbrances created or deleted. |
| As invoices and invoice lines are created, updated, approved and paid, the system automatically makes changes to a variety of other records, including adjustments to spent finances, releasing of encumbrances, and/or updating the order to a paid status. |
Proposed workflow:
Access change log
See
Requirements Board:
Questions:
Question | Status | Conclusion | Comments | ||||||
|---|---|---|---|---|---|---|---|---|---|
|
Work Breakdown Structure:
Features:
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
UI Stories
| Jira Legacy | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
MOD Stories
| Jira Legacy | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|