Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 103 Next »

Goal

Two sprints left to complete CCE Service. Let's continue pushing ahead on Vaccines functionality. Sprint 33 is when we release 3.2.0 around August 30-31.
Team ParrotTeam ILLTeam Malawi

Vaccines

Vaccine Tickets, UI Design and Tech DesignBugs

CCE

Spikes & GuidanceConfiguration Report

Connecting Stock and Requisitions


Performance
(Perf Tests and Optimizations)

New Admin Screen
Reporting Service (for contribution)

Note: We are starting to include Malawi priorities on this backlog grooming in order to improve coordination and transparency between the teams. For example, the core team recently established a new system for Performance Testing, and now the Malawi team is going to build on that by adding performance tests to critical parts of the system, such as Convert to Order, that are key areas for the Malawi implementation.

Vaccines

CCE (MUST)

(Hey Pawel, these top 3 tickets are related/overlapping. Please read them all and divide up the work carefully between devs (or stagger the work)).

  • OLMIS-2619 - Getting issue details... STATUS (MUST) 
    Q: Should the second modal be that big? Nick Reid (Deactivated) This modal is exceptionally long, does it scroll? Is the scrolling done inside of the modal? Sometimes the scrolling modal doesn't work as well when it is long and we might have problems with usability. We should test with different resolutions to see if this causes problems.
    Q: Which model field is serial number? Is it unique ID? There are fields for specific devices that are not in the catalog. Both reference name, barcode, and serial number are those fields.  
    Rachel Powers (Deactivated) will need to provide where the unique ID is coming from. 
    Q    : Should we add new reference name and what exactly is it?  Is this provided by the user? Per Rachel, every device should have a serial number, but this isn't how users refer to the device. The reference name is the less formal name for the device.
    Q: Should the make/model field be visible if type is not selected? Per Rachel, if equipment type is not selected then make/model is disabled but still visible, this is ok. Rachel Powers (Deactivated) to confirm if make/model are separate fields.

  • OLMIS-2921 - Getting issue details... STATUS (MUST)
    Q: Should we update the item after closing the update status modal or after clicking edit? When does this status change affect the backend, after clicking edit? Per Rachel, the system should be updated once the user clicks Update.
    Q: We can see a Edit button on the modal, what is its function? Edit button brings the user to the modal to make edits to the non-functional fields.
    Q:     Should this be a separate state? Nick Reid (Deactivated)
    Q: Should we add a separate endpoint for status update? Chongsun Ahn (Unlicensed) to review design to see what is possible. If this is not separate, then when status is changed, the whole inventory item is updated. 

  • OLMIS-2617 - Getting issue details... STATUS (MUST) 
    Q: Should we be redirected to the update status modal after closing the add/edit modal? Nick Reid (Deactivated): Per Brandon, this should take you back to where you last were, so if you are in the second modal, then you should be redirected to the first modal, or if you are in the first modal and exit, then you should go back to the search screen. Per Nikodem: There might be a case where we update the inventory item, and then we don't see the updated item on the details view. So the data is not reloaded. The state approach is better for this scenario. Per Sam: Need to ensure in these scenarios that the modals don't close when the user clicks on the backdrop. This could cause issues when adding data and then clicking away from modal. User must explicitly close the modal.

  • OLMIS-2915 - Getting issue details... STATUS (MUST)
    Q: If uniqueId reflects serial number should it be DB unique? Per Brandon, there may be cases where the serial number is not completely unique. Per Chongsun, looking at the schema and description of the tickets, the unique ID should be unique across asset types. There should be a constraint. So how should this be enforced, serial number plus make and model? Rachel Powers (Deactivated), Chongsun Ahn (Unlicensed) to confirm.

  • OLMIS-2872 - Getting issue details... STATUS

  • OLMIS-2913 - Getting issue details... STATUS
    Q: Who exactly is DIVO and CCE technician in this context? What rights and permissions have to qualify for these users? Rachel Powers (Deactivated) and Sam Im (Deactivated) to update permissions description in the ticket to reflect which user types have these rights.

  • OLMIS-2608 - Getting issue details... STATUS
    Q: "add support for archived flag to our CSV CCE catalog uploads and downloads (so an admin can upload a new CSV marking some models as archived and that will take effect)" What does it mean to take effect in this case? Per Rachel, this is how we edit what a user can see in the dropdowns when they are adding a device to the CCE Inventory. The make and models that are available in the dropdown for every type should only show if they are active. If they are inactive, they will not show in the list. 
    Q: Is this field required? What is the default value? Yes the archived flag should be required. The default value is active so that it is visible. If this is marked as inactive, it can be marked as active again via the file.

Connecting Stock Management and Requisitions (MUST)

  • OLMIS-2833 - Getting issue details... STATUS  (MUST)
  • OLMIS-2694 - Getting issue details... STATUS (MUST)
    Q: How the migration should work? See the ticket below OLMIS-2830 shows specifics about the migration and provides steps.
    Q: Do we want the migration to go to the database? Paweł Gesek to kickoff a design in dev forum.

  • OLMIS-2830 - Getting issue details... STATUS (MUST)

QA & Testing

Reference UI

Requisition

  (none)

Fulfillment

Reference Data

Stock Management

Auth

  • OLMIS-2902 - Getting issue details... STATUS  (cleaning up tech debt in Auth service; proposed by Team Parrot in Sprint 31)

Platform

Team Malawi

Ben Leibert is identifying priorities and coordinating between teams

  • High priority bugs that will benefit the Malawi implementation to happen right away to be included in the 3.2.0 release at end of August
  • Potentially contribute to admin screens (such as the one listed above under Reference Data)

       Reporting

       Reference Data

  • OLMIS-2758 - Getting issue details... STATUS  (MUST)
  • OLMIS-2912 - Getting issue details... STATUS  (MUST)
    • this one may need more details in the ticket to move it from Roadmap to ToDo
  • OLMIS-2716 - Getting issue details... STATUS  (MUST) (The MW team reported this issue.)
  • OLMIS-2713 - Getting issue details... STATUS  (The MW team reported this issue.)

      Requisition

  • OLMIS-2680 - Getting issue details... STATUS  (MUST)
  • OLMIS-2681 - Getting issue details... STATUS  (MUST)
    • Requisition object will need to understand the format laid out by reference data
    • Requisitions migrated to store a relevant permission string
  • OLMIS-2880 - Getting issue details... STATUS  (MUST)
  • OLMIS-2887 - Getting issue details... STATUS  (MUST)
  • OLMIS-2863 - Getting issue details... STATUS
  • OLMIS-2429 - Getting issue details... STATUS  (Low priority, but also low effort.)
  • OLMIS-2726 - Getting issue details... STATUS
  • OLMIS-2724 - Getting issue details... STATUS
  • OLMIS-2908 - Getting issue details... STATUS  
    • Josh Zamor please weigh in on tech approach of database constraint; also may need group review of whether this is really Critical priority
    • Not a must for this sprint

Team ILL

  • No labels

OpenLMIS: the global initiative for powerful LMIS software