Versions Compared

Old Version 1

changes.mady.by.user Cate Boerema (Deactivated)

Saved on

compared with

New Version Current

changes.mady.by.user Cate Boerema (Deactivated)

Saved on

Key

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

This page contains historical data from the Overall Status Update table on the FOLIO Q2 Q4 2019 Weekly Status Report

...

DateProduct OwnerNotable Risks, Issues and/or Changes
November 29, 2019

Dennis Bridges

Jira Legacy
serverSystem JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-689
 Feature has been included in q4-spillover as there wasn't capacity to implement before feature freeze.

Jira Legacy
serverSystem JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-196
 Has been split. Allocations, transfers and Encumbrances will be included in the Q4 release. The remaining tasks will primarily account for the creation of payment and credit transactions that are the result of processing an invoice. These will updated the impacted budget values based on Fund distribution information on the invoice record. This also includes the work on restricting encumbrance and spending when budgets do not have enough money allocated to cover the costs. These restrictions rely on allowable encumbrance and allowable allocation settings found in each budget. see 
Jira Legacy
serverSystem JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-2167
 to track remaining work.

Jira Legacy
serverSystem JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-697
 Has also been marked as spillover as there is work remaining on ordering in a separate currency and dependancies on UXPROD-2167 for testing and validating that work is truly complete for this issue.

Jira Legacy
serverSystem JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-2050
 Has been split into two issues that will require updated prioritization. 
Jira Legacy
serverSystem JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-2169
 was created to capture small performance fixes and updates that could not be implemented in Q4. While 
Jira Legacy
serverSystem JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-2168
 was created because analysis has revealed that work needed to allow the editing of order cost and quantity information post creation will require significant time to implement.

November 18, 2019

Dennis Bridges

UXPROD-1547 (Check-in and Receiving orders for Packages of material) and UXPROD-916 (Export Library Accounting vouchers) which were previously identified as at risk features will not be release in Q4 as a meaningful amount of progress will not be made on them in time.

UXPROD-689 (Ability to update item record with call number when receiving) remains at risk moving into sprint 77

UXPROD-196 (Value management through transactions.) remains at risk and will likely need to be split as APIs required to create payment transactions are still in progress. Invoices can be marked as Approved and Paid, but may not generate the necessary transaction(s) to mark set aside encumbered monies as expended for the impacted budgets.