Backlog Grooming Sprint 104
Dates: -
3.4 Release Candidate Testing
Release Candidate Testing will begin during this sprint
- Other work should include updating translations for 3.4 release and updating documentation related to 3.4 release
Team Parrot Sprint
Sprint Goal: Finish epics, 3.3.1 patch release and critical bug fixes
Continue if not done in Sprint 103: - OLMIS-4866Getting issue details... STATUS
Do the patch release: - OLMIS-5037Getting issue details... STATUS
Mateusz Kwiatkowski to add ticket for requisition contract test failures - - OLMIS-4930Getting issue details... STATUS
- OLMIS-5041Getting issue details... STATUS this probably won't get done before sprint 104; we can however finish this up early next sprint and leave space for any performance improvements tickets
Bugs: We definitely need to tackle - OLMIS-5073Getting issue details... STATUS and - OLMIS-5064Getting issue details... STATUS (potentially replace some bugs that weren't picked in sprint 103 if not enough capacity)
Perf testing: After early performance testing, verify whether - OLMIS-5076Getting issue details... STATUS and - OLMIS-5075Getting issue details... STATUS need to be tackled and potentially add more tickets
Docs: - OLMIS-5058Getting issue details... STATUS
RC? Are we planning to release first RC this sprint Mary Jo Kochendorfer (Deactivated)?
Each sprint, Team Parrot's sprint will include up to 20% bugs and up to 20% tech debt tickets from the respective backlogs
Team Parrot to use 20% of their capacity to fix the following prioritized bugs:
Team Parrot to use 20% of their capacity to fix the following prioritized Tech Debt tickets:
- Sebastian Brudziński to add Tech Debt backlog here
- 3.4 Release Candidate Testing (Joanna Bebak (Deactivated))
Team Ona Gap
Sprint Goal:
Add reporting stack to CI process, create end-to-end sample, document and release with OpenLMIS v3.4
- - OLMIS-5022Getting issue details... STATUS
- - OLMIS-5024Getting issue details... STATUS
- - OLMIS-4975Getting issue details... STATUS
- - OLMIS-4772Getting issue details... STATUS
- - OLMIS-4778Getting issue details... STATUS
- - OLMIS-4920Getting issue details... STATUS
- - OLMIS-5086Getting issue details... STATUS
- - OLMIS-5087Getting issue details... STATUS
- - OLMIS-5088Getting issue details... STATUS
- - OLMIS-5089Getting issue details... STATUS
- - OLMIS-5090Getting issue details... STATUS
- - OLMIS-5091Getting issue details... STATUS
- - OLMIS-5092Getting issue details... STATUS
- - OLMIS-5093Getting issue details... STATUS
- - OLMIS-5094Getting issue details... STATUS
- - OLMIS-5095Getting issue details... STATUS
- - OLMIS-5096Getting issue details... STATUS
- - OLMIS-5097Getting issue details... STATUS
Future:
- Write human test scripts for the MVP of the reporting stack (What steps do we expect a tester to go through?)
- Figure out how to backup each reporting service
- Write Automated tests for Superset stock status tabular report
- Define the process for restarting process groups in a Nifi docker container that has be restarted
- Test the status of Flowfiles when a docker container is restarted (What happens to them? Are they persisted, are they deleted?)
- - OLMIS-4752Getting issue details... STATUS
Team JSI Gap
Sprint Goal:
Ashraf to add tickets here
- Type your task here, using "@" to assign to a user and "//" to select a due date
Team Mind the Gap
Sprint Goal:
- Tickets related to the following epics will be added as they are created: Nikodem Graczewski (Unlicensed), Łukasz Lewczyński (Deactivated), Chongsun Ahn (Unlicensed) FYI these are the next prioritized features :
- Tech Debt tickets:
- Bugs
- Release Candidate Testing
- Sam & Chongsun in Gdansk: Gdansk agenda 7-30 to 8-3
OpenLMIS: the global initiative for powerful LMIS software