App | Known issue | Workaround | JIRA issue | Product Owner |
---|
Settings > Inventory > Statistical codes | Handle delete of statistical code associated with instance, holdings, or item in a properly manner. | The approach we took for this issue MODINVSTOR-829 should be similar to what needs to be done for the other related issues, addressed in UXPROD-1889 | Jira |
---|
server | FOLIO Issue Tracker |
---|
columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 6ccf3fe4-3301-368a-983e-20c466b11a49 |
---|
key | UXPROD-1889 |
---|
|
| |
Requests | When duplicating a request, the original pickup location selection is not preserved. | Re-select the pickup location. | Jira |
---|
server | FOLIO Issue Tracker |
---|
columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 6ccf3fe4-3301-368a-983e-20c466b11a49 |
---|
key | UIREQ-751 |
---|
|
| Brooks Travis |
eUsage reports plugin | When an agreement links titles harvested from the GOKb, no graphs or CSV reports are available in the Agreements app. | None. Currently the plugin is only working for agreements with titles that were uploaded to the Local KB manually (KBART). | Jira |
---|
server | FOLIO Issue Tracker |
---|
columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 6ccf3fe4-3301-368a-983e-20c466b11a49 |
---|
key | UIPER-97 |
---|
|
| (Kristen Wilson) Index Data / Annika Schröer |
Data import | Jira |
---|
server | FOLIO Issue Tracker |
---|
serverId | 6ccf3fe4-3301-368a-983e-20c466b11a49 |
---|
key | MODDATAIMP-705 |
---|
|
|
| Jira |
---|
server | FOLIO Issue Tracker |
---|
serverId | 6ccf3fe4-3301-368a-983e-20c466b11a49 |
---|
key | MODDATAIMP-705 |
---|
|
| Ann-Marie Breaux |
eholdings | eholdings app now supports exporting package and title+package information. Maximum export - 10,000 titles | No workaround. Awaiting KB enhancements. |
| |
MARC authority | First deletion of a MARC authority record maybe delayed but the record is deleted. | No workaround | Jira |
---|
server | FOLIO Issue Tracker |
---|
serverId | 6ccf3fe4-3301-368a-983e-20c466b11a49 |
---|
key | UIMARCAUTH-159 |
---|
|
| |
Bulk edit | When triggering the bulk edit of item records by submitting a list of holdings HRIDs, the reported number of the updated records might be incorrect. | No workaround | Jira |
---|
server | FOLIO Issue Tracker |
---|
serverId | 6ccf3fe4-3301-368a-983e-20c466b11a49 |
---|
key | UIBULKED-122 |
---|
|
| |
Title Level Requests | In Settings >> Circulation >> Title level requests >> Notice templates IF the TLR is a hold, or there is no item tied to the holding and instance (title), THEN you cannot see the title (or the authors) of the intance instance in the notice. | No workaround | Jira |
---|
server | FOLIO Issue Tracker |
---|
serverId | 6ccf3fe4-3301-368a-983e-20c466b11a49 |
---|
key | CIRC-1558 |
---|
|
| |
Title Level Requests | IF the title level request gets tied to an item, THEN the appropriate request policy (as per the circ rule) is followed for that item EXCEPT when it comes to the TLR notice: The confirmation/cancellation/expiration notice of the request will be the TLR notices (as found here: Settings >> Circulation >> Title level requests >> Notice templates), rather than following the notice policy from the circ rule of that item. | No workaround | No ticket yet to cover this work. | |
Title Level Requests | Requests with the status Closed - pickup expired are causing queue positions to be absent from the queue. For example, if Request A was position 1, and it's status changes to Closed pickup expired, then Position 1 will be absent from the queue. This does not affect the functionality of the queue. | No workaround | CIRC-1589 | |
Item Limits | When a patron reaches the Loan Policy Item Limit at checkout, the error message that appears in the "Item not checked out" pop-up always indicates that the limit is "1", when it could be another number. Item limits work, but the message is incorrect. | Check the Loan Policy to see what the Item Limit is. | Jira |
---|
server | FOLIO Issue Tracker |
---|
columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 6ccf3fe4-3301-368a-983e-20c466b11a49 |
---|
key | UIU-2652 |
---|
|
| Holly Mistlebauer |