1 Status Meanings
2 eUsage
- 2.1 Roadmap
  - 2.1.1 Umbrellaleaf
    - 2.1.1.1 Improve handling of COUNTER API Exceptions
    - 2.1.1.2 Integrate provider lists (look-up)
    - 2.1.1.3 Other features
  - 2.1.2 Not scheduled
    - 2.1.2.1 All issues
    - 2.1.2.2 Automatic maintenance of UDP via aggregator
  - 2.1.3 CoP - Counter API Exceptions
3 eUsage Reports (Plugin Agreements)
- 3.1 Hebis
- 3.2 Others
  - 3.2.1 Open / Draft

Status Meanings

Each status has a certain significance in the development workflow. You can read this under https://folio-org.atlassian.net/wiki/x/8L0o (Product Owners / JIRA status). The Leipzig development team is guided by these specifications.

We use the following Jira status.

Draft
In Refinement
Open
In Progress
In Review
Closed

eUsage

https://folio-org.atlassian.net/browse/UXPROD-576

Please note: The releases mentioned for issues are plans. There is no guarantee that the issues will be ready on the release dates.

Roadmap

Umbrellaleaf

Improve handling of COUNTER API Exceptions

Integrate provider lists (look-up)

Other features

Not scheduled

Release date not yet determined.

All issues

Automatic maintenance of UDP via aggregator

EPIC https://folio-org.atlassian.net/browse/UIEUS-424

CoP - Counter API Exceptions

eUsage Reports (Plugin Agreements)

Hebis

https://folio-org.atlassian.net/browse/UXPROD-5535

Others

https://folio-org.atlassian.net/browse/UXPROD-1253

Issues / Roadmap