Versions Compared

Version Old Version 2 New Version 3
Changes made by

Dennis Bridges

Dennis Bridges

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Jira Legacy
serverSystem Jira
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-3456

Problem(s):

  1. Order numbers in FOLIO can live for multiple fiscal years. Ongoing orders have a tendency to change over time and ideally users can edit things like publish and vendor reference numbers. Not knowing what the recent edit are can make orders confusing and delete old numbers etc means sacrificing historical information that could be valuable for acquisitions workflowshave been can made to invoices makes it difficult to troubleshoot issue
  2. Not having a complete history of invoice changes can mean sacrificing valuable information when a comment is changed etc.

Use Cases & Requirements:

RequirementStatusUse cases
User is shown what field was edited and when it was edited (Date and Time), in local timezone

Status
colourYellow
titlePending


User is shown what the original value was and what new value was input

Status
colourYellow
titlePending


User can filter through list of changes. Filtering on original value, new value or field name

Status
colourYellow
titlePending


User is able to enter a note or reference a note such that it can be seen in the "change log"

Status
colourYellow
titlePending


Changes tracking begins after order has been opened for the first time

Status
colourYellow
titlePending


User can reveal what fields have been edited, if needed.

Status
colourYellow
titlePending


Track changes made by system users. Track updates made by the order to related records. Ie. pieces or encumbrances created or deleted.

Status
colourYellow
titlePending



Proposed workflow:

Access change log

See 

Requirements Board:


Questions:

Question

Status

Conclusion

Comments


Status
colourBlue
titleOpen




Work Breakdown Structure:

Features:

Jira Legacy
serverSystem Jira
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-204

Jira Legacy
serverSystem Jira
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-3456


UI Stories

Jira Legacy
serverSystem Jira
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQuery(issuekey in linkedIssues("UXPROD-3456") AND project in (UIOR, UIREC, UIV, UIF, UINV, UIORGS, STFORM, UIAC, UIPFO, UIPFCONT, UIPCITEM, UIPFINT, UIPFPOL)) OR (issuekey in linkedIssues("UXPROD-204") AND project in (UIOR, UIREC, UIV, UIF, UINV, UIORGS, STFORM, UIAC, UIPFO, UIPFCONT, UIPCITEM, UIPFINT, UIPFPOL))
serverId01505d01-b853-3c2e-90f1-ee9b165564fc

MOD Stories

Jira Legacy
serverSystem Jira
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQuery(issuekey in linkedIssues("UXPROD-204") AND project in (MODORDERS, MODVEND, EDGOAIPMH, EDGORDERS, MODCRED, MODFISTO, MODFUND, MODGOBI, MODINVOICE, MODINVOSTO, MODOAIPMH, MODORDSTOR, MODREC, MODORGS, MODINV, MODCONF, EDGOAIPMH, mod-organizations-storage, mod-organizations, MODEBSNET)) OR issuekey in linkedIssues("UXPROD-3456") AND project in (MODORDERS, MODVEND, EDGOAIPMH, EDGORDERS, MODCRED, MODFISTO, MODFUND, MODGOBI, MODINVOICE, MODINVOSTO, MODOAIPMH, MODORDSTOR, MODREC, MODORGS, MODINV, MODCONF, EDGOAIPMH, mod-organizations-storage, mod-organizations, MODEBSNET)
serverId01505d01-b853-3c2e-90f1-ee9b165564fc