Skip to end of metadata
Go to start of metadata

Suggest ideas for FOLIO reports and dashboards here

Dynamic release data with weekly status updates

Q1 2019 Features in JIRA (updates dynamically)

Functional Features Today

Getting issues...

NFRs (Non-Functional Requirements) Today

Getting issues...

See the Q1 2019 Release Dashboard and the Chalmers Release Dashboard in JIRA for more charts and click-through to feature details.

See FOLIO Quality Dashboard for bi-weekly updates on software quality.

Weekly Updates

Report Date

Overall Status Update

Q1 Feature Count on Report Date




Cate Boerema

Circulation critical path review

  • Core Functional is still behind on extending loan rules (originally targeted to be done by mid sprint 56). Now work may continue beyond sprint 58.
  • Vega was also delayed with patron notices and, therefore, have not been blocked by this.
  • Due to delays in extending loan rules and the need for more tech design, we are no longer tracking to deliver the functionality needed to make patron notices effective in Q1
  • Request policy basic CRUD is complete, but the work to make the policies effective will be delayed due to delays in extending loan rules
  • Backend timezone compliance (not part of the original Q1 scope) has been prioritized for Vega, as, without it, due dates and times will not be accurate.
  • Core Functional is also behind on hold shelf expiry period work, but, again, Vega is not ready to start on the next step (request expiration)

  • Vega has uncovered some new work in calendar and closed library due date management that needs to be prioritized (stories still TBD)In summary:
  • Good news: additional backend developer (Anatolii from EPAM) joining Core Functional team (ramping up this week and full-time as of next)

Ann-Marie working on tagging projects in SonarCloud to make it easier for POs, scrummasters and tech leads to review test coverage by development team and/or app

Getting issues...

Getting issues...

Click to view status update history

Q1 2019 Release Features (Functional) by Status

Getting issues...

Q1 2019 Release Features (NFR) by Status

Getting issues...




Feature is waiting to be picked up by PO.  


Feature is  being worked on by the PO.  Discussions are happening with the SIGs and sub-groups, mock-ups are being created.  Analysis is underway.

Analysis Complete

PO analysis is complete.  Stories are written and mockups have been created.

In Progress

Analysis is complete and development is underway.  While it is often the case that we begin development on some aspects of a feature before the PO’s analysis work has been completed, please do not move a feature into Development (In Progress) until after Analysis is Complete.  This is important so we can maintain visibility into what features that have remaining PO work.

In Review

Most or all stories in the feature are In Review (being tested).


All stories in the feature have passed test and are closed.  Feature is complete.

Product Owner Updates

DateProduct OwnerNotable Risks, Issues and/or Changes

As noted in several weekly status reports, the Core Functional team is behind schedule. As a result, several features will not make the Q1 release. The following features have been reassigned to Q2:

Click to view product owner update history

Q1 2019 Spillover and At Risk Issues

At Risk IssuesQ1 stories and features that are at risk (meaning they may spill over)

Getting issues...

Spillover FeaturesFeatures originally targeted for Q1 which have been shifted to Q2 due to insufficient capacity

Getting issues...

Spillover StoriesUser stories originally targeted for Q1 which have been shifted to Q2 due to insufficient capacity

Getting issues...


The focus of Q1 2019 is delivering the features required by Chalmers to go live.  For this reason, we will take a closer look at those features in this portion of the report.  See the Chalmers Release Dashboard in JIRA for these and more click-through reports.

NOTE: There are also  Getting issues...  (UXPROD features) that have not yet been ranked by Chalmers.  As these features are ranked, we should expect the features needed below to increase.

Remaining Features Needed by Chalmers to Go-Live 

Epic Link Fix For Versions (non-archived)
Q4 2018 Q1 2019 Q2 2019 Unscheduled T:
Agreements 3 1 0 0 4
Allow for the creation and management of vendor records 0 1 0 0 1
Batch Importer (Bib/Acq) 0 0 1 0 1
Codex 0 2 0 0 2
eHoldings App 0 1 2 0 3
ERM Navigation 3 0 0 0 3
GDPR 0 0 0 8 8
General UX 0 1 0 0 1
Inventory 0 0 3 0 3
Item states 0 1 0 0 1
Licences 1 0 0 0 1
Loan Rules and Policies 0 5 0 1 6
Loans 0 2 1 3 6
Notes/Comments 0 1 0 0 1
Order Materials and Services 0 1 0 0 1
Orders and Inventory Integration Phase 1 0 0 1 0 1
Patron notices 0 3 0 1 4
Receiving and Checking-in of Physical Items 0 0 1 0 1
Requests 0 5 2 2 9
SIP2: Protocol for self-checkout 0 0 1 0 1
Staff slips 0 1 0 0 1
Tags - Basic 0 1 2 1 4
Tags - Central Management 0 0 1 0 1
None 1 6 0 0 7
Total Unique Issues: 8 32 15 16 71
Showing 24 of 24 statistics.
View in JIRA

Chalmers Go-Live Features at Risk in Q1

These may be carried over into Q2 2018 (either entirely or in part)

Key Summary Assignee Status epic link Labels development team

Chalmers for Go-Live Feature With No PO

Key Summary Fix Version/s epic link

Features Needed by Chalmers for Go-Live

Q4 2018 Release History

Current featuresFeatures targeted for Q1 release as of today
  • Getting issues... Functional
  • Getting issues... NFR
Baseline release features

Baseline features targeted at beginning of quarter (January 14, 2019)

  • Getting issues... Functional
  • Getting issues... NFR