Versions Compared

Key

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

...

  • Only HTML changed
  • Search file might be too big – ideally only table would be changed

Should PR to Core


Solution

Open-External-URL

  • Needs unit tests
  • Needs documentation
  • Could be used to fix print url hacks in other places – should be addressed separately

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

Table Horizontal Scrollbar

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

  • This should be brought over to CORE
  • Unit tests are needed

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


Should be Moved

All the changes for the MW-UI were made directly in that repository, which means git can't merge changes. Fixing this would mean forking the original repository, and creating an image from that forked repository that is used in the MW-UI.
The benefit is this would allow git to automatically merge most code changes. As the core product releases new versions over time, git upstream code can be pulled into MW-UI while preserving the local modifications. This greatly reduces ongoing maintenance effort of conducting each upgrade.

...

 and Batch Approval

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

  • There are plans to merge these feature changes back to core – getting this code out of MW-UI and into a place where make a PR would be trivial makes sense
  • Fork OpenLMIS/openlmis-requisition-ui to OpenLMIS-Malawi/openlmis-requisition-ui
  • Having a correct fork would make maintenance and merging changes easier

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

Requisition Service

  • There are a handful of changes here, that either should

...

  • be refactored to smaller changes instead of forking a file
  • Until that happens, the changes should live in OpenLMIS-Malawi/openlmis-requisition-ui

Needs Improvement


Solution

Login Service

Was there a ticket for this commit??

...

  •  is tightly coupled to other "start up" actions,

...

  •  should be refactored to use an extension mechanism
    • Either an event OR $q.all w/$filter

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

TB Quarterly Warning

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

...

...

  •  to add an alert - this can be accomplished by decorating the controller method

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

Alphabetically Sorted Product Dropdowns

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

  • The change is made

...

  • in add-product-modal.html - this can be done in a reusable/testable way by:
    • add decorator to controller
    • sort products in factory

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

  • To change a link, we are:
    • Forking the controller file, and adding two new methods
    • Forking the HTML to change the link
  • This can be done more cleanly by
    • decorating the controller to change the link (no need to touch the HTML)
    • refactoring the controller to use a factory to produce the link
    • refactor to use external-url method (mentioned above)
  • Target directories

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

Uncertain


Solution

Requisition Initiate

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

File

  • Most of the changes to this file have been to maintain warning message
  • CORE won't follow this design direction

OpenLMIS-Facility-Program-Select

  • Seems to be added to fix other

...

...

    •  Could you look into if we

...

...

  • Looks like many of the changes are to support the report-url changing
  • This could be done without forking, probably
  • Git history here doesn't have many ticket numbers, so its hard to figure out WHY changes were made

Tickets created by Weronika Ciecierska (Unlicensed) as a result of discussion with Nick Reid (Deactivated):

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

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

...

-

...

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

...

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

...

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

...

440

Report

  • Looks like many of the changes are to support the report-url changing
  • This could be done without forking, probably
  • Git history here doesn't have many ticket numbers, so its hard to figure out WHY changes were made