Page Comparison

Suggest ideas for FOLIO reports and dashboards here

Page Properties

label	jirareport

Dynamic release data with weekly status updates

Q3 2019 Features in JIRA (updates dynamically)

Functional Features Today

Jira Legacy

server	System Jira
jqlQuery	project = 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
count	true
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc

Dynamic release data with weekly status updates

Functional Features ( ! OR labels = EMPTY)

Q3 2019 Features in JIRA (updates dynamically)

NFRs (Non-Functional Requirements) Today

Jira Legacy

server	System Jira
jqlQuery	project = 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
count	true
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc

NFRs (Non-Functional Requirements) Today

Jira Legacy

server	System Jira
jqlQuery	project = 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
count	true
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc

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

See /wiki/spaces/DQA/pages/2654395 for bi-weekly updates on software quality.

Weekly Updates

Report Date

Overall Status Update

Q3 Feature Count on Report Date

Functional

NFR

2019-10-08

Started sprint 74
Platform Q3.2 updates (dev):
- Chalmers-related performance and stability issues:
  - mod-authtoken 2.3.0 and mod-permissions 5.8.3 released with performance improvement, available for both Q3.1 and Q3.2. Brings overall request time improvements, incl. Check-in/Check-out. To be verified on Bugfest environments when hotfixes are installed there.
  - Jira Legacy
    server System Jira
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key UICHKIN-111
    back in OPEN for another review. Additional, tasks ongoing
  - - Jira Legacy
      server System Jira
      serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
      key MODAT-51
      reports ~35% request time spent in mod-authtoken/mod-permissions for a warm system with new improvements. Depending on trhe bugfest envs numbers, Platform team will look at additional improvements.
    - Problems to be addressed by other teams are still incomplete:
      - Jira Legacy
        server System Jira
        serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
        key MODNOTIFY-54
    - The ticket to replicate check-in/check-out performance issues on the Perf test env by adding more realistic circulation data is pending:
      Jira Legacy
      server System Jira
      serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
      key CIRC-466
  - Jira Legacy
    server System Jira
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key UXPROD-1820
    New development work (RMB 27.x related) has been resumed this week:
    - Jira Legacy
      server System Jira
      serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
      key MODINVSTOR-256
      pending verification
    - Jira Legacy
      server System Jira
      serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
      key MODINVSTOR-349
      enabler for
      Jira Legacy
      server System Jira
      serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
      key UIIN-564
      is back in development
Platform Q3.2 updates (devops):
- Standard release related activities have been completed last week (what remain is ad-hoc hotfix releases) and the team has resumed focus on Continuous Deployment work, namely:
- Jira Legacy
  server System Jira
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key FOLIO-2227
  which consists of the following sub-tasks:
  - Jira Legacy
    server System Jira
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key FOLIO-2275
  - Jira Legacy
    server System Jira
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key FOLIO-2265
  - Jira Legacy
    server System Jira
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key FOLIO-2267
  - Jira Legacy
    server System Jira
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key FOLIO-2268
- Additionally the following CI problems are being addressed:
  - Jira Legacy
    server System Jira
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key FOLIO-2060
  - Jira Legacy
    server System Jira
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key FOLIO-2276
  - Jira Legacy
    server System Jira
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key FOLIO-2282
  - Jira Legacy
    server System Jira
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key FOLIO-2237
Q3.2 (Daisy) release:
- Daisy out on 2nd October
- Remaining problems will be addressed through hotfix releases. Jira tickets that should be addressed through hotfix releases will be labelled as ^q3.2-2019-hotfix^
- Jira Legacy
  server System Jira
  jqlQuery labels = q3.2-2019-hotfix
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
- Proposal for Q3.2 bugfix/support release cycle:
  - continue publishing bugfix releases for issues tagged as ^q3.2-2019-hotfix^ until and including Jan 2020 (one month after Q4 is out)
- What about Q3.1 bugfixes?
- release spreadsheet: https://docs.google.com/spreadsheets/d/1DKV8rf3kD7QAz57etqA-C2FqHHLZmRVmMZFobvDszn8/edit#gid=0

2019-10-01

Mid Sprint 73
Platform Q3.2 updates (dev):
- Various security-related issues brought up last week took precedence over other work:
  - Jira Legacy
    server System Jira
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key OKAPI-763
    solution for
    Jira Legacy
    server System Jira
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key FOLIO-2287
  - Jira Legacy
    server System Jira
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key OKAPI-764
    solution for
    Jira Legacy
    server System Jira
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key FOLIO-2286
  - Jira Legacy
    server System Jira
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key RMB-478
- Chalmers-related performance and stability issues:
  - Jira Legacy
    server System Jira
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key UICHKIN-111
    all individual backend tickets have been addressed (for list see previous report) besides:
  - - Jira Legacy
      server System Jira
      serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
      key MODAT-51
    - Jira Legacy
      server System Jira
      serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
      key MODPERMS-67
    - Jira Legacy
      server System Jira
      serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
      key MODUSERS-150
    - Problems to be addressed by other teams are still incomplete:
      - Jira Legacy
        server System Jira
        serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
        key MODSOURCE-76
      - Jira Legacy
        server System Jira
        serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
        key MODNOTIFY-54
    - The ticket to replicate check-in/check-out performance issues on the Perf test env by adding more realistic circulation data is pending:
      Jira Legacy
      server System Jira
      serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
      key CIRC-466
  - Jira Legacy
    server System Jira
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key UXPROD-1820
    New development work (RMB 27.x related) has been resumed this week:
    - Jira Legacy
      server System Jira
      serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
      key MODINVSTOR-256
      pending verification
    - Jira Legacy
      server System Jira
      serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
      key MODINVSTOR-349
      enabler for
      Jira Legacy
      server System Jira
      serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
      key UIIN-564
      is back in development
Platform Q3.2 updates (devops):
- Standard release related activities have been completed last week (what remain is ad-hoc hotfix releases) and the team has resumed focus on Continuous Deployment work, namely:
- Jira Legacy
  server System Jira
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key FOLIO-2227
  which consists of the following sub-tasks:
  - Jira Legacy
    server System Jira
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key FOLIO-2275
  - Jira Legacy
    server System Jira
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key FOLIO-2265
  - Jira Legacy
    server System Jira
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key FOLIO-2267
  - Jira Legacy
    server System Jira
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key FOLIO-2268
- Additionally the following CI problems are being addressed:
  - Jira Legacy
    server System Jira
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key FOLIO-2060
  - Jira Legacy
    server System Jira
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key FOLIO-2276
  - Jira Legacy
    server System Jira
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key FOLIO-2282
  - Jira Legacy
    server System Jira
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key FOLIO-2237
Q3.2 (Daisy) release:
- release pending on a bugfix for
  Jira Legacy
  server System Jira
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key UIU-1271
  which should be available related today
- during
  Jira Legacy
  server System Jira
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key UIU-1271
  another problem has been discovered,
  Jira Legacy
  server System Jira
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key STCOR-392
  , will be addressed by a Stripes bugfix release after Q3.2
- Bugfix release cycle for Q3.1, Q3.2 and preview release for Q4 should be established ASAP. Currently it's not clear for how long we'd like to support Q3.1 (and going forward Q3.2) and release bugfixes. Proposal:
  - end-of-life Q3.1 asap – e.g mid-October (depends on Chalmers upgrade plans)
  - continue publishing bugfix releases (critical defects only) for Q3.2 until and including Jan 2020
- release spreadsheet: https://docs.google.com/spreadsheets/d/1DKV8rf3kD7QAz57etqA-C2FqHHLZmRVmMZFobvDszn8/edit#gid=0

Cate Boerema (Deactivated)

Chalmers is live!
Bugs and enhancement requests are beginning to come in:
Jira Legacy
server System Jira
jqlQuery filter=11808
count true
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
Have created first pass at release notes accessible from here: Release Notes
Q3 needs to be wrapped up in JIRA. There are still ~10 open UXPRODs

Jira Legacy

server	System Jira
jqlQuery	project = 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-10-01) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
count	true
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc

Jira Legacy

server	System Jira
jqlQuery	project = 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-24) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
count	true
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc

2019-09-24

Jakub Skoczen

Started Sprint 73
Platform Q3.2 updates (dev):
- Jira Legacy
  server System Jira
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key UXPROD-1820
  RMB 27.x related:
  - Jira Legacy
    server System Jira
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key RMB-468
    enabler for
    Jira Legacy
    server System Jira
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key MODINVSTOR-256
    has been completed and awaits roll-out this sprint
  - Jira Legacy
    server System Jira
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key MODINVSTOR-349
    enabler for
    Jira Legacy
    server System Jira
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key UIIN-564
    requires functionality that was missing from
    Jira Legacy
    server System Jira
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key RMB-385
    and has been BLOCKED and postponed to the next sprint to allow the Platform team to focus on performance issues this sprint
- Chalmers-related performance and stability issues:
  - Jira Legacy
    server System Jira
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key UICHKIN-111
    has been broken down into a set of analysis tasks last sprint:
    - Jira Legacy
      server System Jira
      serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
      key CIRC-448
    - Jira Legacy
      server System Jira
      serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
      key CIRC-452
    - Jira Legacy
      server System Jira
      serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
      key CIRC-453
    - Jira Legacy
      server System Jira
      serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
      key CIRC-464
  - The analysis uncovered various performance problems in individual storage and low-level BL APIs. Some of the problems are addressed directly by the Platform team while others are being addressed by the teams responsible for individual modules.
    - Jira Legacy
      server System Jira
      serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
      key MODUSERS-150
    - Jira Legacy
      server System Jira
      serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
      key MODPERMS-66
    - Jira Legacy
      server System Jira
      serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
      key MODAT-49
    - Jira Legacy
      server System Jira
      serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
      key MODAT-51
    - Jira Legacy
      server System Jira
      serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
      key MODCAL-50
      (this problem has surfaced during check-out, not check-in, see UICHKOUT-541)
    - Problems to be addressed by individual teams:
      - Jira Legacy
        server System Jira
        serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
        key MODSOURCE-76
      - Jira Legacy
        server System Jira
        serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
        key MODNOTIFY-54
  - Additionally the Platform team will work to reproduce perf issues locally (so far the analysis used only the logfiles, limiting how thorough it can be)
    - Jira Legacy
      server System Jira
      serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
      key CIRC-466
  - Stability problems being addressed:
    - Jira Legacy
      server System Jira
      serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
      key MODPERMS-64
Platform Q3.2 updates (devops):
- Standard release related activities have been completed last week (what remain is ad-hoc hotfix releases) and the team has resumed focus on Continuous Deployment work, namely:
- Jira Legacy
  server System Jira
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key FOLIO-2227
  which consists of the following sub-tasks:
  - Jira Legacy
    server System Jira
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key FOLIO-2275
  - Jira Legacy
    server System Jira
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key FOLIO-2265
  - Jira Legacy
    server System Jira
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key FOLIO-2267
  - Jira Legacy
    server System Jira
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key FOLIO-2268
- Additionally the following CI problems are being addressed:
  - Jira Legacy
    server System Jira
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key FOLIO-2060
  - Jira Legacy
    server System Jira
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key FOLIO-2276
  - Jira Legacy
    server System Jira
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key FOLIO-2237
Q3.2 (Daisy) release:
- Module release deadline: 11th September, midnight GMT
- Bugfix release deadline: 25th September, midnight GMT
- release spreadsheet: https://docs.google.com/spreadsheets/d/1DKV8rf3kD7QAz57etqA-C2FqHHLZmRVmMZFobvDszn8/edit#gid=0

Cate Boerema (Deactivated)

Loan policy testing in BugFest was blocked until today due to
Jira Legacy
server System Jira
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key CIRC-461
It is now blocked due to insufficient bandwidth on my part. I'll do my best
Currently working to keep Core Functional's backlog ahead of development. This means reviewing and clarifying Sean's Loan policy features and helping Charlotte and Laura with the Call number features
Very concerned about lack of dev-ready backlog across the board: https://issues.folio.org/secure/RapidBoard.jspa?rapidView=130
One more hotfix coming soon for Chalmers to address
Jira Legacy
server System Jira
columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key CHAL-29
and
Jira Legacy
server System Jira
columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key CHAL-30
Only one more 3.2 bug still open for Core: Functional but it's likely not to make it at this point. This is not a must-have for Chalmers:
Jira Legacy
server System Jira
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key UIIN-725

Jira Legacy

server	System Jira
jqlQuery	project = 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-24) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
count	true
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc

Jira Legacy

server	System Jira
jqlQuery	project = 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-24) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
count	true
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc

2019-09-17

Jakub Skoczen

Mid Sprint 71

Platform Q3.2 updates (dev):

Jira Legacy
server System Jira
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key UXPROD-1820
RMB 27 released, ongoing work in particular modules to roll out new functionality:
- Jira Legacy
  server System Jira
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key RMB-385
  enabler for
  Jira Legacy
  server System Jira
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key MODINVSTOR-349
  which in turn addresses
  Jira Legacy
  server System Jira
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key UIIN-564
- Jira Legacy
  server System Jira
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key RMB-468
  enabler for resolution of following perf issue:
  Jira Legacy
  server System Jira
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key MODINVSTOR-256
Remaining Chalmers-related issues:
- brought up today by Cate, to be discussed at Platform's standup
- Jira Legacy
  server System Jira
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key UICHKIN-111
  has been broken down into following optimization tickets:
  - Jira Legacy
    server System Jira
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key CIRC-448
  - Jira Legacy
    server System Jira
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key CIRC-452
  - Jira Legacy
    server System Jira
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key CIRC-453

Platform Q3.2 updates (devops):

Focus on Daisy release activities

Jira Legacy
server System Jira
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key FOLIO-2262
Jira Legacy
server System Jira
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key FOLIO-2252
Jira Legacy
server System Jira
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key FOLIO-2259
Jira Legacy
server System Jira
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key FOLIO-2258
Jira Legacy
server System Jira
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key FOLIO-2257

Jira Legacy

server	System Jira
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	UXPROD-1827

Jira Legacy
server System Jira
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key FOLIO-2011
will be showcased at the PO meeting on Wednesday
Remaining FOLIO-1827 blockers:
Jira Legacy
server System Jira
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key FOLIO-2252
Jira Legacy
server System Jira
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key FOLIO-2056
, which is blocked on:
- Jira Legacy
  server System Jira
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key FOLIO-2249
Jira Legacy
server System Jira
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key FOLIO-2227
to be addressed in sprint 72

Q3.2 (Daisy) release:

Module release deadline: 11th September, midnight GMT
Bugfix release deadline: 25th September, midnight GMT
release spreadsheet: https://docs.google.com/spreadsheets/d/1DKV8rf3kD7QAz57etqA-C2FqHHLZmRVmMZFobvDszn8/edit#gid=0

Cate Boerema (Deactivated)

Development:

Have hotfixed several bugs for Chalmers:
Jira Legacy
server System Jira
jqlQuery labels in (hotfixed) AND status = closed ORDER BY key ASC
count true
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
Still working through several important issues:
- Jira Legacy
  server System Jira
  columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key CIRC-440
  - Development complete. Testing in folio-snapshot now (looks good so far!)
- Jira Legacy
  server System Jira
  columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key UICHKIN-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 Legacy
  server System Jira
  columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key UIIN-687
  - Work Ryan did to
  Jira Legacy
  server System Jira
  columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key STCOR-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 Legacy
  server System Jira
  columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key CHAL-29
- Jira Legacy
  server System Jira
  columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key CHAL-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 Legacy
server System Jira
columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key CHAL-29
and
Jira Legacy
server System Jira
columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key CHAL-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.

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

See /wiki/spaces/DQA/pages/2654395 for bi-weekly updates on software quality.

Weekly Updates

Report Date

Overall Status Update

Q3 Feature Count on Report Date

Functional

NFR

2019-10-02

Cate Boerema (Deactivated)

Q3 RELEASED
User-facing release notes available here: Q3 2019 (Daisy) Release Notes
Features closed/completed in Q2 2019: Release Notes

Jira Legacy

server	System Jira
jqlQuery	project = 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-0910-1702) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
count	true
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc

Jira Legacy

server	System Jira
jqlQuery	project = 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-0910-1702) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
count	true
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc

Click to view status update history

Q3 2019 Release Features (Functional) by Status

Jira Legacy

server	System Jira
jqlQuery	project = 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
count	true
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc

Jira Charts

border	true
showinfor	false
server	System Jira
jql	project%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
statType	statuses
chartType	pie
width
isAuthenticated	true
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc

Q3 2019 Release Features (NFR) by Status

Jira Legacy

server	System Jira
jqlQuery	project = 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
count	true
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc

Jira Charts

border	true
showinfor	false
server	System Jira
jql	project%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
statType	statuses
chartType	pie
width
isAuthenticated	true
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc

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

Date	Product Owner	Notable Risks, Issues and/or Changes
8/1/19	Ann-Marie Breaux (Deactivated)	Closed 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	Dennis Bridges	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
9/30/19	Ann-Marie Breaux (Deactivated)	UXPROD-1124 (Assign tags to finance records): no work done in Q3, since the finance records structures were evolving; moved the whole feature to Q4 Split the following Q3 features: UXPROD-255 (Filter by tags) is followed by UXPROD-2090 (Tags cleanup) UXPROD-1125 (Assign tags to order records); backend work completed in Q3, to be followed in Q4 by UXPROD-2073 (Assign tags to order records and filter by them) UXPROD-1379 (CRUD for action profiles) is followed by UXPROD-2074 (Bring action profiles to life) UXPROD-1380 (CRUD for field mapping profiles) is followed by UXPROD-2075 (MARC field mapping profile details) UXPROD-1768 (NFR Data Import work in Q3) is followed by UXPROD-2076 (NFR Data Import work in Q4) UXPROD-1769 (Remaining job and match profile work) is followed by UXPROD-2077 (Part 2) UXPROD-1805 (SRS MARC-Inventory Instance refinement) is followed by UXPROD-2078 (Last bits)

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 Legacy

server	System Jira
jqlQuery	project = 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
count	true
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc

(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

server	System Jira
jql	filter%3D11044
ystattype	customfield_10002
chartType	twodimensional
isAuthenticated	true
numberToShow	50
xstattype	fixfor
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc

Chalmers for Go-Live Feature With No PO

Jira Legacy

server	System Jira
columns	key,summary,fixversions,epic link
maximumIssues	20
jqlQuery	filter=11046
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc

Features Needed by Chalmers for Go-Live

Jira Charts

border	true
showinfor	false
server	System Jira
jql	filter%20%3D%20%22Chalmers%20Go-Live%20Features%20(Regardless%20of%20Release)%22
statType	statuses
chartType	pie
isAuthenticated	true
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc

Q3 2012 Release History

Metric

Description

Current features

Features targeted for Q3 release as of today

Jira Legacy

server	System Jira
jqlQuery	project = 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
count	true
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc

Functional

Jira Legacy

server	System Jira
jqlQuery	project = 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
count	true
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc

NFR

Baseline release features

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

Jira Legacy

server	System Jira
jqlQuery	project = 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
count	true
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc

Functional

Jira Legacy

server	System Jira
jqlQuery	project = 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
count	true
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc

NFR

...

Versions Compared

Old Version 73

New Version 74

Key

Dynamic release data with weekly status updates

Q3 2019 Features in JIRA (updates dynamically)

Functional Features Today

Dynamic release data with weekly status updates

Q3 2019 Features in JIRA (updates dynamically)

NFRs (Non-Functional Requirements) Today

NFRs (Non-Functional Requirements) Today

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

See /wiki/spaces/DQA/pages/2654395 for bi-weekly updates on software quality.

Weekly Updates

Report Date

Overall Status Update

Q3 Feature Count on Report Date

Functional

NFR

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

See /wiki/spaces/DQA/pages/2654395 for bi-weekly updates on software quality.

Weekly Updates

Report Date

Overall Status Update

Q3 Feature Count on Report Date

Functional

NFR

Click to view status update history

Q3 2019 Release Features (Functional) by Status

Q3 2019 Release Features (NFR) by Status

Product Owner Updates

Chalmers

Remaining Features Needed by Chalmers to Go-Live

Chalmers for Go-Live Feature With No PO

Features Needed by Chalmers for Go-Live

Q3 2012 Release History