Log inSkip to main contentSkip to sidebar
Loading…
FOLIO Issue Tracker
  • Dashboards
  • Projects
  • Issues
  • Give feedback to Atlassian
  • Help
    • Jira Core help
    • Keyboard Shortcuts
    • About Jira
    • Jira Credits
  • Log In
    • Download JIRA Client

Export - CSV (All fields)

Export - CSV (Current fields)

Comma (,) Semicolon (;) Vertical bar (|) Caret (^)

  1. Bug CIRC-1783
    Very slow check out behavior observed in Nolana Hotfix #1
  2. Bug CIRC-1860
    missing permission circulation-storage.circulation-rules.get for mod-circulation_0 timer
  3. Bug CIRC-1835
    Very slow check out behavior: Orchid CSP 3
  4. Bug CIRC-1737
    Calendar timetable is absent for requested date
  5. Bug CIRC-1680
    [Nolana BugFix] cross-tenant policy id causing 500 errors during circ. transactions
  6. Bug CIRC-1676
    500 error is shown after the item checkout
  7. Bug CIRC-1668
    cross-tenant policy id causing 500 errors during circ. transactions
  8. Bug CIRC-1743
    [Orchid] Calendar timetable is absent for requested date
  9. Bug CIRC-1734
    TLR: user able to place title level request when TLR is not enabled
  10. Bug CIRC-1663
    DELETE /circulation/loans with query params trigger bulk DELETE /circulation/loans
  11. Bug CIRC-1624
    On SNAPSHOT, ACTUAL COST lost items are being closed as "Lost and paid" before "Lost item fee (actual cost)" has been billed
  12. Bug CIRC-1610
    TLR: Item assigned to recall should not be renewable
  13. Bug CIRC-1577
    Date parsing in mod-circulation does not handle loanDate/dueDate without timezone information but allows saving loans without that information
  14. Bug CIRC-1576
    TLR (pages) aren't being fulfilled when there is an available non-requestable item at the chosen service point
  15. Bug CIRC-1575
    500 Error When Placing TLR/Instance Requests via mod-patron When There Are "Available" but not Pageable Items
  16. Bug CIRC-1540
    Receive error when attempting to check-in items on Lotus BugFest
  17. Bug CIRC-1583
    Rolling due date loan policy with fixed due date schedule(due date limit) fails when the schedule range begins after the checkout date
Refresh results
{"errorMessages":["jqlTooComplex"],"errors":{}}
[{"id":-1,"name":"My open issues","jql":"assignee = currentUser() AND resolution = Unresolved order by updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":true},{"id":-2,"name":"Reported by me","jql":"reporter = currentUser() order by created DESC","isSystem":true,"sharePermissions":[],"requiresLogin":true},{"id":-4,"name":"All issues","jql":"order by created DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-5,"name":"Open issues","jql":"resolution = Unresolved order by priority DESC,updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-9,"name":"Done issues","jql":"statusCategory = Done order by updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-3,"name":"Viewed recently","jql":"issuekey in issueHistory() order by lastViewed DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-6,"name":"Created recently","jql":"created >= -1w order by created DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-7,"name":"Resolved recently","jql":"resolutiondate >= -1w order by updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-8,"name":"Updated recently","jql":"updated >= -1w order by updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false}]
0.3
0
  • Atlassian Jira Project Management Software
  • About Jira
  • Report a problem

Powered by a free Atlassian Jira open source license for Index Data. Try Jira - bug tracking software for your team.

Atlassian