Backlog Grooming Sprint 105

Dates: 02 Aug 2018 - 15 Aug 2018

3.4 Release Candidate Testing

Release Candidate Testing during this sprint

Other areas of focus after the release: contract tests, functional tests, next gap feature work

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:

key	summary	type	priority	status	labels

Loading...

Refresh

Team Parrot to use 20% of their capacity to fix the following prioritized Tech Debt tickets:

key summary type priority status labels

Loading...
Refresh

Finalize the 3.4 release of the reporting stack and scope facility registry integration with mCSD standard.

Tickets:

Future:

Ashraf to add tickets here

OLMIS-4948 - Getting issue details... STATUS
OLMIS-4938 - Getting issue details... STATUS
OLMIS-5065 - Getting issue details... STATUS
OLMIS-2989 - Getting issue details... STATUS
OLMIS-5174 - Getting issue details... STATUS
Type your task here, using "@" to assign to a user and "//" to select a due date

Sprint Goal:

Release Candidate Testing
- Fix bugs assigned to our team as needed
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
- OLMIS-4842 - Getting issue details... STATUS (Ticket writing in progress)
- Create tickets for UI mockups
OLMIS-5136 - Getting issue details... STATUS (Question in the ticket for Elias, if eLMIS has implemented this then we will want to work on this ticket, but if not we can move this to a future sprint.)

20% Tech Debt tickets

OLMIS-4569 - Getting issue details... STATUS
- If time, pull in Requisition functional test cases (Initiate, Submit, Authorize, Approve are most important)