Sprint Goal / Focus
- License Term Management
Sprint Schedule
- Sprint: 135
- Start Mon 7 Mar
- Finish Fri 18 Mar
- Sprint Board
- Jira Sprint: 1214
- Release: 2022.2 Morning Glory
- Sprint 142: Module Release Deadline
- Backend 22 June 2022
- Frontend 24 June 2022
- Sprint 145: Bugfix Deadline (29 July 2022)
- Sprint 142: Module Release Deadline
Sprint Capacity
Team Availability: Schedule | Calendar
Notes / Exceptions:
- NA
Lead Roles:
- Code Review: Ethan Freestone
- QA: Owen Stephens
QA Environment: folio-snapshot
Info | ||
---|---|---|
| ||
|
Navigation
Table of Contents |
---|
Expand | ||
---|---|---|
| ||
|
Sprint Planning
- not in sprint
or @ - in sprint
Info | ||
---|---|---|
| ||
|
Sprint Focus
Feature ID | Issue ID | Sprint Backlog? | Notes / Estimates / Actions | ||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| For Lotus Bugfix In Progress: https://github.com/folio-org/mod-agreements/tree/fix-clone-agreement | ||||||||||||||||||||||||||||||||||
|
| To follow
To be done as extension of
| |||||||||||||||||||||||||||||||||
|
|
| |||||||||||||||||||||||||||||||||
|
|
| |||||||||||||||||||||||||||||||||
|
|
| |||||||||||||||||||||||||||||||||
|
| Preparatory work for surfacing external package data in Agreements. Refdata values are based on Gokb, but these are platform neutral More complex are package identifiers (likely to be namespaced)
|
Rolled Over From Previous Sprint
For Development
Feature ID | Issue ID | Sprint Backlog? | Notes / Estimates / Actions | ||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
| In Code Review | |||||||||||||||||||||||||||||||||
|
| Returned to dev to
Switches to agreementsViewRoute manifest, which doesn't have OA context
| |||||||||||||||||||||||||||||||||
|
| From Slack: Refactoring is done, atm I'm working on displaying the fields, so if I managed to display the right data, I start writing test for the new components. | |||||||||||||||||||||||||||||||||
|
| Ethan has messaged Orgs team to address implementation approach. | |||||||||||||||||||||||||||||||||
|
For QA
Feature ID | Issue ID | Sprint Backlog? | Notes / Estimates / Actions |
---|---|---|---|
For Release Prep
Feature ID | Issue ID | Sprint Backlog? | Notes / Estimates / Actions |
---|---|---|---|
Bugfix Cycle
Feature ID | Issue ID | Sprint Backlog? | Notes / Estimates / Actions |
---|---|---|---|
Brought In
Feature ID | Issue ID | Sprint Backlog? | Notes / Estimates / Actions | ||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
| Can model around CoverageFieldArray in agreements | ||||||||||
|
Removed
Feature ID | Issue ID | Sprint Backlog? | Notes / Estimates / Actions | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Blocked pending stripes-kint-components migration/refactor |
Sprint Summary
ERM
Jira Legacy | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Dashboard
Jira Legacy server System JiraJIRA columnIds issuekey,summary,issuetype,assignee,status,components columns key,summary,type,assignee,status,components maximumIssues 20 jqlQuery labels = dashboard and Sprint = 1214 serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
Other
Jira Legacy | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|