Versions Compared

Key

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

Goal: Continue to work towards feature goals for 3.3 (vaccine stock based requisition, Receiving/POD, Local Fulfillment, etc.), make progress on Administration screens and critical needs for implementers.Goal: Finishing touches and bug fixing (blockers and criticals), regression testing

Dates:  -  

Note

LAST Sprint!!! Regression Testing time....

Side Note for Parrot: We've noticed there have been more tickets being created recently. Are some of these musts that need to get done? Can you please make sure to flag if we are missing critical tasks that were recently created by the team. All rollovers from Sprint 48 must be finished.

...

CCE

  •  
    Jira Legacy
    serverSystem JIRA
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-3191
     (MUST)

Local Fulfillment

  •  
    Jira Legacy
    serverSystem JIRA
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-4195
     (From Showcase: TO DISCUSS AT SPRINT Q&A Thursday; we want to make sure the AC are clear that the "No Lot Defined" collapses with the row above, similar to Stock Management)

UI

  •  
    Jira Legacy
    serverSystem JIRA
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-4026
     (Ticket was mostly done, but has 2-3 issues in the comments still to address Brandon Bowersox-Johnson to add comment to specify exactly what is left to complete)

Bugs that must be fixed prior to regression testing

  • ALL Blocker and Critical bugs must be fixed this sprint before regression testing can begin. These bugs should include performance bugs.

Jira Legacy
serverSystem JIRA
columnskey,summary,type,assignee,reporter,priority,status,resolution,epic name,fixversions,labels
maximumIssues10
jqlQueryfilter=20523 order by Priority
serverId448ba138-230b-3f91-a83e-16e7db1deed1



...



Note
titleRegression Testing will only begin after everything above this line is complete.


Regression Testing

We plan to start testing after all blocking and critical bugs are fixed and tested.

See plan located here: 3.3 Regression & Release Candidate Test Plan

For all bug fixes during regression testing, we will require re-push reviews via pull requests or have more reviewers for any change.

  •  
    Jira Legacy
    serverSystem JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-4342
     (Sam Im (Deactivated))
  •  
    Jira Legacy
    serverSystem JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-3498
     (Sebastian Brudziński & Brandon Bowersox-Johnson, per discussion Jakub was going to work on this during the regression testing)
  •  Sam Im (Deactivated) to create testing tickets for Team ILL Sprint 49


Infrastructure

  •  
    Jira Legacy
    serverSystem JIRA
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-41154286
      (Nice to have Sebastian Brudziński can decide.)

Platform

We can do the following during regression testing since it should

...

impact. Perhaps not wait to the last minute given it is unclear how long it will take. 

  •  

    API Live DocsOur live documentation stopped working due to a dependency issue in NPM.  For the time being we've unblocked development by removing live doc generation, leaving dead links and no live docs on our documentation page.  We'll fix this by increasing the priority of simplifying our live documentation generation:

    Jira Legacy
    serverSystem JIRA
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-3708
     (MUST)
  •  
    Jira Legacy
    serverSystem JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-4295

To Discuss:

Jira Legacy
serverSystem JIRA
serverId448ba138-230b-3f91-a83e-16e7db1deed1
keyOLMIS-3653
 (Sebastian Brudziński to check both fulfillment and POD to make sure it is correct)


Team ILL

  •  
    Jira Legacy
    serverSystem JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-4219
     Chongsun Ahn (Unlicensed)

Community Meeting (Brandon Bowersox-JohnsonTenly Snow (Deactivated))

  •  
    Jira Legacy
    serverSystem JIRA
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-4350
      - Tenly & Brandon to meet on  to discuss sharing form on tech and Slack (question) 
  •  
    Jira Legacy
    serverSystem JIRA
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-4351
  •  

    For 3.3 release: Tenly Snow (Deactivated) will create tickets for each of the following

    •  

      Blog 

      Jira Legacy
      serverSystem JIRA
      serverId448ba138-230b-3f91-a83e-16e7db1deed1
      keyOLMIS-4345

    •  

      Newsletter 

      Jira Legacy
      serverSystem JIRA
      serverId448ba138-230b-3f91-a83e-16e7db1deed1
      keyOLMIS-4346

    •  

      Community email 

      Jira Legacy
      serverSystem JIRA
      serverId448ba138-230b-3f91-a83e-16e7db1deed1
      keyOLMIS-4347

    •  

      Targeted email to vaccine stakeholders 

      Jira Legacy
      serverSystem JIRA
      serverId448ba138-230b-3f91-a83e-16e7db1deed1
      keyOLMIS-4348

  •  Tenly Snow (Deactivated) to add ticket for Review of 2 page for Gavi demo 
    Jira Legacy
    serverSystem JIRA
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-4349

Demo Environment Prep


Performance Testing

  •  
    Jira Legacy
    serverSystem JIRA
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-4352
     to coordinate work on this epic: 
    Jira Legacy
    serverSystem JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-4275