Versions Compared

Key

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


Suggest ideas for FOLIO reports and dashboards here

Page properties
labeljirareport
Jira
serverFOLIO Issue Tracker
jqlQueryproject = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND (labels != NFR OR labels = EMPTY) AND fixVersion was "Q3 2019" ON (2019-07-02) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
counttrue
serverId6ccf3fe4-3301-368a-983e-20c466b11a49

Dynamic release data with weekly status updates

Q3 2019 Features in JIRA (updates dynamically)

Functional Features Today


Jira
serverFOLIO Issue Tracker
jqlQueryproject = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND (labels != NFR OR labels = EMPTY) AND fixVersion = "Q3 2019" ORDER BY cf[10002] ASC, assignee ASC, summary ASC
counttrue
serverId6ccf3fe4-3301-368a-983e-20c466b11a49

NFRs (Non-Functional Requirements) Today

Jira
serverFOLIO Issue Tracker
jqlQueryproject = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND labels = NFR AND fixVersion = "Q3 2019" ORDER BY cf[10002] ASC, assignee ASC, summary ASC
counttrue
serverId6ccf3fe4-3301-368a-983e-20c466b11a49

See the Q3 2019 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

Q3 Feature Count on Report Date



Functional

NFR

2019-09-17

Jakub Skoczen

  • Mid Sprint 71
  • Platform Q3.2 updates (dev):
    • Jira
      serverFOLIO Issue Tracker
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyUXPROD-1820
       RMB 27 released, ongoing work in particular modules to roll out new functionality:
      • Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyRMB-385
         enabler for 
        Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyMODINVSTOR-349
         which in turn addresses 
        Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyUIIN-564
      • Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyRMB-468
         enabler for resolution of following perf issue: 
        Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyMODINVSTOR-256
         
    • Remaining Chalmers-related issues:
      •  brought up today by Cate, to be discussed at Platform's standup
      • Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyUICHKIN-111
         has been broken down into following optimization tickets:
        • Jira
          serverFOLIO Issue Tracker
          serverId6ccf3fe4-3301-368a-983e-20c466b11a49
          keyCIRC-448
        • Jira
          serverFOLIO Issue Tracker
          serverId6ccf3fe4-3301-368a-983e-20c466b11a49
          keyCIRC-452
        • Jira
          serverFOLIO Issue Tracker
          serverId6ccf3fe4-3301-368a-983e-20c466b11a49
          keyCIRC-453
  • Platform Q3.2 updates (devops):
    • Focus on Daisy release activities
      • Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyFOLIO-2262
         
      • Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyFOLIO-2252
      • Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyFOLIO-2259
      • Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyFOLIO-2258
      • Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyFOLIO-2257
    • Jira
      serverFOLIO Issue Tracker
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyUXPROD-1827

      • Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyFOLIO-2011
         will be showcased at the PO meeting on Wednesday
      • Remaining FOLIO-1827 blockers:
      • Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyFOLIO-2252
         
      • Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyFOLIO-2056
        , which is blocked on:
        • Jira
          serverFOLIO Issue Tracker
          serverId6ccf3fe4-3301-368a-983e-20c466b11a49
          keyFOLIO-2249
      • Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyFOLIO-2227
         to be addressed in sprint 72
  • Q3.2 (Daisy) release:

Cate Boerema 

Development:

  • Have hotfixed several bugs for Chalmers: 
    Jira
    serverFOLIO Issue Tracker
    jqlQuerylabels in (hotfixed) AND status = closed ORDER BY key ASC
    counttrue
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
  • Still working through several important issues:
    • Jira
      serverFOLIO Issue Tracker
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyCIRC-440
       - Development complete.  Testing in folio-snapshot now (looks good so far!)
    • Jira
      serverFOLIO Issue Tracker
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyUICHKIN-111
       - Backend optimizations being worked by Core Platform.  With Zak and Marc back at work, Core Functional will look at the proposal for frontend optimizations in grooming today (UICHKIN-112).  RA SIG has discussed performance requirements and check in is needed to take less than one second for barcode scanners.  Should be 1/3 of a second for RFID scanners.  See performance requirements page: Performance requirements for daily operation of the FOLIO system 
    • Jira
      serverFOLIO Issue Tracker
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyUIIN-687
       - Work Ryan did to 
      Jira
      serverFOLIO Issue Tracker
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keySTCOR-388
       may have helped but didn't solve the problem.  He continues to investigate.  This turns out to be easier to reproduce than initially thought (it doesn't take hours to build this latency - just a bit of activity across inventory, requests and users).  New, clarified repro steps should help with locating the problem
  • Some new circ issues are popping up as Chalmers continues to migrate data.  These may require additional hotfixes:
    • Jira
      serverFOLIO Issue Tracker
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyCHAL-29
    • Jira
      serverFOLIO Issue Tracker
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyCHAL-30

Testing:

  • Request test cases have been fleshed out in TestRail (steps and expected behavior in all tests)
  • I've assigned myself all the loan policy test cases, as they need fleshing out - CIRC-440 revealed that we have not done sufficient testing in this area
  • Recent performance issues and bugs like 
    Jira
    serverFOLIO Issue Tracker
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyCHAL-29
     and 
    Jira
    serverFOLIO Issue Tracker
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyCHAL-30
     make me wonder if our performance and load testing is sufficient.

Planning:

  • RA SIG invited Cap planning group to discuss non-MVP features.  There are many features implementing institutions feel are deal-breakers for go live (see 2019-9-16 Resource Access Meeting Notes).  General agreement was that we need to get requirements ready so that, when/if development resources become available, they are ready to pick up.    


Jira
serverFOLIO Issue Tracker
jqlQueryproject = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND (labels != NFR OR labels = EMPTY) AND fixVersion was "Q3 2019" ON (2019-09-17) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
counttrue
serverId6ccf3fe4-3301-368a-983e-20c466b11a49

Jira
serverFOLIO Issue Tracker
jqlQueryproject = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND labels = NFR AND fixVersion was "Q3 2019" ON (2019-09-17) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
counttrue
serverId6ccf3fe4-3301-368a-983e-20c466b11a49

Click to view status update history

Q3 2019 Release Features (Functional) by Status

Jira
serverFOLIO Issue Tracker
jqlQueryproject = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND (labels != NFR OR labels = EMPTY) AND fixVersion = "Q3 2019" ORDER BY cf[10002] ASC, assignee ASC, summary ASC
counttrue
serverId6ccf3fe4-3301-368a-983e-20c466b11a49

Jira Charts
bordertrue
showinforfalse
serverFOLIO Issue Tracker
jqlproject%20%3D%20uxprod%20AND%20type%20%3D%20%22new%20feature%22%20AND%20(resolution%20not%20in%20(duplicate%2C%20%22Won't%20Do%22)%20OR%20resolution%20is%20EMPTY)%20AND%20(labels%20!%3D%20NFR%20OR%20labels%20%3D%20EMPTY)%20AND%20fixVersion%20%3D%20%22Q3%202019%22%20ORDER%20BY%20cf%5B10002%5D%20ASC%2C%20assignee%20ASC%2C%20summary%20ASC%20
statTypestatuses
chartTypepie
width
isAuthenticatedtrue
serverId6ccf3fe4-3301-368a-983e-20c466b11a49

Q3 2019 Release Features (NFR) by Status

Jira
serverFOLIO Issue Tracker
jqlQueryproject = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND labels = NFR AND fixVersion = "Q3 2019" ORDER BY cf[10002] ASC, assignee ASC, summary ASC
counttrue
serverId6ccf3fe4-3301-368a-983e-20c466b11a49

Jira Charts
bordertrue
showinforfalse
serverFOLIO Issue Tracker
jqlproject%20%3D%20uxprod%20AND%20type%20%3D%20%22new%20feature%22%20AND%20(resolution%20not%20in%20(duplicate%2C%20%22Won't%20Do%22)%20OR%20resolution%20is%20EMPTY)%20AND%20labels%20%3D%20NFR%20AND%20fixVersion%20%3D%20%22Q3%202019%22%20ORDER%20BY%20cf%5B10002%5D%20ASC%2C%20assignee%20ASC%2C%20summary%20ASC%20
statTypestatuses
chartTypepie
width
isAuthenticatedtrue
serverId6ccf3fe4-3301-368a-983e-20c466b11a49

Status

Definition

Open 

Feature is waiting to be picked up by PO.  

Draft 

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).

Closed

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


Product Owner Updates


DateProduct OwnerNotable Risks, Issues and/or Changes
8/1/19Ann-Marie BreauxClosed 2 features: UXPROD-1447 (block edit of Inventory Instances with underlying MARC Bib in SRS) and UXPROD-1220 (Assign tags to Data Import profiles)
8/15/19

The following mvp features were closed: UXPROD-1603, UXPROD-717, UXPROD-721, UXPROD-719, UXPROD-1776, UXPROD-1665, UXPROD-189 see list

Following Cap plan updates I have removed the Q3 2019 fixed version from all features not marked as cap-mvp in order to clarify what will be delivered in Q3. This includes: UXPROD-204, UXPROD-194, UXPROD-1018, UXPROD-1036, UXPROD-1025, UXPROD-1564 see list

The Q3 2019 fixed version has also been removed from issues that are still currently in draft, as analysis and creation of user stories is ongoing and development work will not begin in Q3. This includes: UXPROD-689, UXPROD-1578, UXPROD-1547, UXPROD-697 see list
















Click to view product owner update history

Chalmers 

One focus of Q3 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 

Jira
serverFOLIO Issue Tracker
jqlQueryproject = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND status != closed AND "Rank: Chalmers" is EMPTY AND (labels not in (NFR, mandatory, technical) OR labels is EMPTY) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
counttrue
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
 (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 

Jira Charts
serverFOLIO Issue Tracker
jqlfilter%3D11044
ystattypecustomfield_10002
chartTypetwodimensional
isAuthenticatedtrue
numberToShow50
xstattypefixfor
serverId6ccf3fe4-3301-368a-983e-20c466b11a49

Chalmers for Go-Live Feature With No PO

Jira
serverFOLIO Issue Tracker
columnskey,summary,fixversions,epic link
maximumIssues20
jqlQueryfilter=11046
serverId6ccf3fe4-3301-368a-983e-20c466b11a49

Features Needed by Chalmers for Go-Live

Jira Charts
bordertrue
showinforfalse
serverFOLIO Issue Tracker
jqlfilter%20%3D%20%22Chalmers%20Go-Live%20Features%20(Regardless%20of%20Release)%22
statTypestatuses
chartTypepie
isAuthenticatedtrue
serverId6ccf3fe4-3301-368a-983e-20c466b11a49




Q3 2012 Release History

MetricDescription
Current featuresFeatures targeted for Q3 release as of today
  • Jira
    serverFOLIO Issue Tracker
    jqlQueryproject = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND (labels != NFR OR labels = EMPTY) AND fixVersion = "Q3 2019" ORDER BY cf[10002] ASC, assignee ASC, summary ASC
    counttrue
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    Functional
  • Jira
    serverFOLIO Issue Tracker
    jqlQueryproject = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND labels = NFR AND fixVersion = "Q3 2019" ORDER BY cf[10002] ASC, assignee ASC, summary ASC
    counttrue
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    NFR
Baseline release features

Baseline features targeted at beginning of quarter (July 2, 2019)

  • Jira
    serverFOLIO Issue Tracker
    jqlQueryproject = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND (labels != NFR OR labels = EMPTY) AND fixVersion was "Q3 2019" ON (2019-07-02) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
    counttrue
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    Functional
  • Jira
    serverFOLIO Issue Tracker
    jqlQueryproject = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND labels = NFR AND fixVersion was "Q3 2019" ON (2019-07-02) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
    counttrue
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    NFR