Versions Compared

Old Version 26

changes.mady.by.user Mary Jo Kochendorfer

Saved on

compared with

New Version Current

changes.mady.by.user Nikodem Graczewski

Saved on

Key

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

Goal: Squash bugs for the  To prepare for a 3.2.1 release . Judiciously continue with F&E features and performance improvements.

Grooming Question: There have been discussions around modifying the release process this time. I'd like to make sure we are clearly communicating the plan to the team. Brandon Bowersox-Johnson do you have an update from the conversations with Josh Zamor?

UPDATE: No decisions yet about the 'release candidate' process or doing a 'slow down and go careful' release for 3.2.1. So for now we are grooming priorities on this page for a squash-bug-and-release scenario, but that could change before sprint 36 begins.

Issue: Malawi faces time-outs when configurations are incorrect. Is there a way to provide an error versus timing out? See the recent slack exchange here

BUGS

There are a lot of bugs. I'm still reviewing and prioritizing. Please let me know which are top priority for you and what the impact of the bug is.

...

candidate at the end of October (~Oct 25 2017). See Release Candidate Process.  Team ILL will focus on Performance.  Team Parrot will focus on fixing bugs and the MUST tickets until performance tickets are available. BUGS are in priority order in the backlog. 


Bugs

Go to backlog, they are in priority order (and there are 17 of them).

Image Added

These two bugs in the backlog are assigned to Team ILL

  • Jira Legacy
    serverSystem JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-31513137
     Requisition (Malawi fixed this on their side already (Team ILL)
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)System JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-31483163
     Requisition  (MUSTTeam ILL)

Requisitions

  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)System JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-32132700
     Requisition  (MUST)
    • We didn't take this ticket as there is a lot of unanswered questions.
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-31703164
     Requisition  (MUST)
    • Jira Legacy
      serverJIRA (openlmis.atlassian.net)
      serverId448ba138-230b-3f91-a83e-16e7db1deed1
      keyOLMIS-3076
      • How do we want to approach this ticket? If we do a check before rejecting and then reject the requisition someone can still initiate a requisition in between.
      • There is no mockup.
      • Should it be only warning or should the newer requisition be deleted when we click the reject?
      • Maybe performance improvement would be to create/update rows in one database request?

    F&E

    • Jira Legacy
      serverJIRA (openlmis.atlassian.net)
      serverId448ba138-230b-3f91-a83e-16e7db1deed1
      keyOLMIS-3144
      Jira Legacy
      serverJIRA (openlmis.atlassian.net)
      serverId448ba138-230b-3f91-a83e-16e7db1deed1
      keyOLMIS-3167
       Reference Data
      396
       (MUST)
      • How many values do we want to include in the CSV file for performance testing?
      • It is highly unlikely that this endpoint will work in less than 0.5 s as every item has to be parsed.
      • What is configure ISA page? Is it the page with upload export?

    Stock Management

    • Jira Legacy
      serverJIRA (openlmis.atlassian.net)
      serverId448ba138-230b-3f91-a83e-16e7db1deed1
      keyOLMIS-3126
       Batch Requisition
      3246
       (MUST) 
    • Ticket for creating more demo data (maybe for Team ILL)

    Admin Screens/ Configuration Reporting

    • Jira Legacy
      serverJIRA (openlmis.atlassian.net)
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId448ba138-230b-3f91-a83e-16e7db1deed1
      keyOLMIS-3215
       Requisition
      2217
       (MUST) Sam Im (Deactivated) there are still open questions in the ticket.
      • Won't it be better to use current implementation of reset password and send email with link to password change page?
    • Jira Legacy
      serverJIRA (openlmis.atlassian.net)
      serverId448ba138-230b-3f91-a83e-16e7db1deed1
      keyOLMIS-3201
      Jira Legacy
      JIRA (openlmis.atlassian.net)
      servercolumnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId448ba138-230b-3f91-a83e-16e7db1deed1
      keyOLMIS-31372697
       (Core team to continue looking into and figure out a plan of action)Team ILL - Sam to work with Chongsun and Josh on questions in this ticket before it can be worked on)

    CCE

    • Jira Legacy
      serverJIRA (openlmis.atlassian.net)
      serverId448ba138-230b-3f91-a83e-16e7db1deed1
      keyOLMIS-31403197

    Reference UI

    • Jira Legacy
      serverJIRA (openlmis.atlassian.net)
      serverId448ba138-230b-3f91-a83e-16e7db1deed1
      keyOLMIS-31083161
       (Nick Reid (Deactivated), needs to be filled out)
    • and more.... what are the top priorities?

    CCE

    •  Team ILL (this could be fast)
    • Jira Legacy
      serverJIRA (openlmis.atlassian.net)
      serverId448ba138-230b-3f91-a83e-16e7db1deed1
      keyOLMIS-

    ...

    • 3195
       Team ILL
    • Jira Legacy
      serverJIRA (openlmis.atlassian.net)
      serverId448ba138-230b-3f91-a83e-16e7db1deed1
      keyOLMIS-396
       (Shall we break this up or not?)

    Stock Management

    • 2443
       Team ILL
    • Jira Legacy
      serverJIRA (openlmis.atlassian.net)
      serverId448ba138-230b-3f91-a83e-16e7db1deed1
      keyOLMIS-2733
    • Ticket for creating more demo data (maybe for Team ILL)

    Admin Screens/ Configuration Reporting

    Sam Im (Deactivated) are these completely ready for work? Are they in priority order

    • 3260
       Team ILL
    • Jira Legacy
      serverJIRA (openlmis.atlassian.net)columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolutionSystem JIRA
      serverId448ba138-230b-3f91-a83e-16e7db1deed1
      keyOLMIS-27583240
       Team ILL

    Low Priority

    • Jira Legacy
      columns
      serverJIRA (openlmis.atlassian.net)
      key,summary,type,created,updated,due,assignee,reporter,priority,status,resolutionserverId448ba138-230b-3f91-a83e-16e7db1deed1
      keyOLMIS-22172772
       Sam Im (Deactivated) there are still open questions in the ticket.wait)
    • Jira Legacy
      serverJIRA (openlmis.atlassian.net)columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId448ba138-230b-3f91-a83e-16e7db1deed1
      keyOLMIS-26972773
       (wait)

    Platform

    • Set up Demo environment for TechNet presentation (Team ILL - Sam to work with Chongsun and Josh on questions in this ticket before it can be worked on)

    ...

    • Jira Legacy
      serverJIRA (openlmis.atlassian.net)
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      System JIRA
      serverId448ba138-230b-3f91-a83e-16e7db1deed1
      keyOLMIS-3164

    Reference UI

    • Jira Legacy
      serverJIRA (openlmis.atlassian.net)
      serverId448ba138-230b-3f91-a83e-16e7db1deed1
      keyOLMIS-3161
       (this could be fast)
      3196
       (already in sprint 35) — Team ILL retrospective idea "pipeline not rejecting, notifiying developer, and preventing deployment to test"
    • "automated tests are not visible/documented in a way implementers and stakeholders can read them" — Team ILL retrospective idea
    • "No checks on test quality/confidence" — Team ILL retrospective idea
    • "Not sure how to write testing stuff in tickets" — Team ILL retrospective idea
    • Pull together performance testing progress/results and present to Product Committee? (Team ILL) 
    • Jira Legacy
      serverSystem JIRA (openlmis.atlassian.net)
      serverId448ba138-230b-3f91-a83e-16e7db1deed1
      keyOLMIS-31953256
       
    • Jira Legacy
      serverJIRA (openlmis.atlassian.net)
      serverId448ba138-230b-3f91-a83e-16e7db1deed1
      keyOLMIS-2443

    Low Priority

    • Jira Legacy
      serverJIRA (openlmis.atlassian.net)
      serverId448ba138-230b-3f91-a83e-16e7db1deed1
      keyOLMIS-2772
    • Jira LegacyserverJIRA (openlmis.atlassian.net)serverId448ba138-230b-3f91-a83e-16e7db1deed1keyOLMIS-2773(Maybe... for the implementers' guide?) Team ILL

    UI Performance Sprint Spike for Team ILL (75%)

    Goals: 

    • Get UI Performance metrics so we can track our progress
      • Get sample data (from MW), put it on our test servers, do manual testing
        (Using core OpenLMIS back-end services and front-end UI app.)
        • Steps/Tasks: 
          1. Get MW data
          2. Identify worst case user/s (which user account, which Facility/ies, which Program/Essential Medicines, ...)
          3. Load data into PerfTest server
          4. Run automated tests using worst case user
          5. Run manual tests/exploratory testing to discover UI performance priorities
            (within Requisitions and Orders)
          6. Use Daily Standup meetings to prioritize and turn ideas into action
        • Risk: The Malawi code-base is customized, so that codebase may have different issues.
      • Capture Before and After states to tell our story
        • Use network and browser tools to simulate LMIC internet connectivity speeds/latency/intermittent connectivity
    • Get UI Performance into an acceptable state
      • Define what is acceptable for non-functional performance
      • Turn issues/problems into ticket assignments for Team Parrot

    Re-Supply Ticket Writing for Team ILL (25%) 

    For Planning Only

    Malawi-UI

    Nick Reid (Deactivated) is this really something we should be taking on prior to a release?

    ...

    • Jira Legacy
      serverJIRA (openlmis.atlassian.net)
      serverId448ba138-230b-3f91-a83e-16e7db1deed1
      keyMW-419
      Jira Legacy
      serverJIRA (openlmis.atlassian.net)
      serverId448ba138-230b-3f91-a83e-16e7db1deed1
      keyMW-437
      Partially completed in 
    • Malawi-Performance


    Jira Legacy
    serverSystem JIRA

    ...

    ...

    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-

    ...

    Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyMW-511
    • Fix is related to work in OLMIS-2956

    3113
     (Team ILL)

    Requests from Malawi

    Ben Leibert and Christine Lenihan, please make sure the following tickets are in priority order so that we can review for the next backlog grooming call on  . If bugs come in after that, please make sure to flag prior to  so we can review prior to planning.Mary Jo pasted the following from sprint 35. Please delete or prioritize.

    • Jira Legacy
      serverJIRA (openlmis.atlassian.net)
      serverId448ba138-230b-3f91-a83e-16e7db1deed1
      keyOLMIS-3147
       (MJ/Ben to speak with Malawi team to see if we can get more information on the desired state or willingness to use workarounds like send emails to spamcan simply set up email rules for now.)

    • Jira Legacy
      serverJIRA (openlmis.atlassian.net)
      serverId448ba138-230b-3f91-a83e-16e7db1deed1
      key

      MALAWISUP

      OLMIS-

      128

      2829
       (

      also identified for the gap analysis) unskipping a period
    • Jira Legacy
      serverJIRA (openlmis.atlassian.net)
      serverId448ba138-230b-3f91-a83e-16e7db1deed1
      keyOLMIS-3157
       (Did Malawi fork this page? Could the team check the APIs? Malawi will check the APIs)

    • Jira Legacy
      serverJIRA (openlmis.atlassian.net)
      serverId448ba138-230b-3f91-a83e-16e7db1deed1
      keyOLMIS-2829
       (Not urgent, but perhaps worth mentioning so it isn't forgotten.)Not urgent, but perhaps worth mentioning so it isn't forgotten.)


    Goal: Squash bugs for the 3.2.1 release. Judiciously continue with F&E features and performance improvements.

    Grooming Question: There have been discussions around modifying the release process this time. I'd like to make sure we are clearly communicating the plan to the team. Brandon Bowersox-Johnson do you have an update from the conversations with Josh Zamor?

    UPDATE: No decisions yet about the 'release candidate' process or doing a 'slow down and go careful' release for 3.2.1. So for now we are grooming priorities on this page for a squash-bug-and-release scenario, but that could change before sprint 36 begins.

    Issue: Malawi faces time-outs when configurations are incorrect. Is there a way to provide an error versus timing out? See the recent slack ex