Versions Compared

Old Version 10

changes.mady.by.user Jag Goraya

Saved on

compared with

New Version 11

changes.mady.by.user Jag Goraya

Saved on

Key

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

Sprint Goal / Focus

  •  Integration with Organizations

Sprint Schedule

  • Sprint: 63
  • Quarter: 2019 Q2
  • Start / Planning Tuesday 7 May, 3pm UK
  • Merge Cutoff Friday 17 May, 2pm UK 
  • End / Turnover Monday 20 May, 10am UK
  • Retrospective: Wed 22 May, 2:30pm UK


Sprint Capacity

Team Availability: Schedule

  • 320 hours (~ full dev strength)

Notes / Exceptions:

  • 6 May UK Public Holiday, so shortened sprint.
  • 7-10 May ELAG: no additional QA support
  • 8, 14, 15 May: No PO availability 

Lead Roles:

QA Environment: folio-testing

Navigation

Table of Contents

Expand
titleSprint Planning Agenda
  1. Sprint Goal / Focus
  2. Sprint Capacity
  3. Review sprint candidates 
  4. Agree technical approach / define key implementation tasks
  5. Finalise estimates / costings
  6. Confirm sprint scope
  7. Confirm first actions


Expand
titleSprint Retrospective Agenda
  1. Review Retro Board (10 mins)
  2. Voting (2 mins)
  3. Discussion (15 mins)
  4. Summary Actions (3 mins)


Sprint Planning  

 

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions


Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-189

Kurt Nordstrom

Previously: BE 16h FE 0h 

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-1597

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-132

steve.osguthorpe

Previously BE 15h FE 8h

Needs updates to web-toolkit, so Ian Ibbotson (Use this one) or steve.osguthorpe

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-1520

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-162

John Fereira md331 (Deactivated)

Previously

  • BE 4h FE 16h
  • ERM-179 can proceed without the back-end sub-issues.
  • ERM-180 is dependent on the back-end tasks.

(warning) needed for 

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-163
 which is also scheduled in this sprint.


Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-1520

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-163

(tick)

Previously BE 0h FE 8h 

(warning) needs 

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-162
 which is scheduled in this sprint

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-1601

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-220

(tick)


BE2h  FE 16h

(warning) needed for 

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-165
 which is also scheduled in this sprint.

Does not include the workflow to include filters. Ideally they would 

Adding an organization to an agreement will create a new link record.

  • Entity: subscriptionAgreementOrg
  • JSON: Orgs array including those Entities.
  • subscriptionAgreementOrg has name and ID.

TODO

  • Backend (all changes to Org) (2h)
    • Rename UUID from VendorsID to OrganizationID
    • Remove orgRef call 
    • Check for and enforce duplicate Organization assignment to role
    • Remove source URI
  • Front-end (8h-16h)
    • Use ui-plugin-find-organizations
    • Update data returned
    • Create UI (non-cards)

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-1601

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-219

(tick)

BE 1h  FE 16h

  • Backend (all changes to Org) (1h)
    • Rename UUID from VendorsID to OrganizationID
    • Remove orgRef call 
    • Check for and enforce duplicate Organization assignment to role
    • Remove source URI
  • Front-end (8h-16h)
    • Use ui-plugin-find-organizations
    • Update data returned
    • Create UI (non-cards)

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-1300

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-165

(tick)

Requires 

  • Jira Legacy
    serverSystem Jira
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyUXPROD-1544
  • Jira Legacy
    serverSystem Jira
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyUXPROD-1601
     

tinymce.emotions_dlg.warning UXPROD-1601 is scheduled for this sprint

Concerns:

  • Permissions to view Organizations and passwords

TODO:

  • Backend (16h)
    • Refactor organization API structure for mod-licenses
    • Refactor organization API structure for mod-agreements
    • Validate modOrganizations behaviour
    • Configure embedded Organizations record
  • Frontend (16h)
    • Display interface data using Card design


Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-1660

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-198

(tick)

Previously: PR to be submitted

  • Ready for Code Review.

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-1159

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-184

Kurt Nordstrom

Previously BE 20h FE 20h

Previously: 

  • To store in db to circumvent OKAPI non-persistence issue.

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-92

Kurt Nordstrom

No further work needed (apart from submitting)

Previously:

  • PR to be submitted for work completed so far. 
  • Integration tests to be resolved separately.

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-49

Owen Stephens

Permission sets to be applied.

There needs to be a higher level discussion about how these groups are defined and categorised, and can be re-used.

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-1513

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-217

(tick)
  • What do we post to the back-end?
    • JSON scheme submit_package
    • single operation

TODO:

  • Needs UI
  • Error message descriptions
  • Large import file (asynchronous handling)
  • Define underscore fields notation

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-1517

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-215

(error)

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-1548

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-186

Claudia Malzer

Previously: BE 0h FE 8h 

  • In General FOLIO Settings app
  • Code in ui-agreements

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-218

John Fereira



Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-190

John Fereira



Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-193


John Fereira

Previously: Looks like it needs resolving in web-toolkit, so Ian Ibbotson (Use this one) or steve.osguthorpe


Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-199

(tick)Merged. Just needs closing now. 


Sprint Retrospective

Expand
titleSprint Retrospective Agenda
  1. Review Retro Board (10 mins)
  2. Voting (2 mins)
  3. Discussion (15 mins)
  4. Summary Actions (3 mins)