This page outlines improvements and technical debt that needs to happen to the OpenLMIS-UI. Tickets listed on this page are may not be ready for work, and can actively be picked up once placed on a backlog grooming page.

Bootstrap Resources

When working on OpenLMIS design or user interface issues, please consult the following resources.

• OpenLMIS design documentation outlines OpenLMIS recommended workflows, form layout, and writing guidelines. Individual designs may break these rules, but the OpenLMIS community recommends against this.
• Wire-frame template library which should be used to start mocks-up and quickly work through content designs.
• OpenLMIS Reference-UI Styleguide which illustrates basic UI styles, layouts, and components - along with the working code to generate them. Use this resource if creating hi-fidelity mockups or working OpenLMIS-UI code.
• UI/UX WTF is a place to catalog inconsistencies that are not ready to become a JIRA ticket

UI Github Repositories

• Dev-UI to v5

Semantically Versioned Repositories

• UI Components to v5.1.1
• UI Layout to v5.0.2
• Auth UI to v5.0.3
• Reference Data UI to v5.2.0
• Requisition UI to v5.1.1
• Fulfillment UI to v5.0.3
• Report UI to v5.0.3

Milestone Versioned Repositories

• Reference UI to v5.0.3

Features Backlog

Bugs

Consistency

• 
• 
• 
• 
• 
•  (NR: OLMIS-1354 & OLMIS-2510 might intersect with this, but doing some work across all services here would be good) 

It is too easy to click off the modal in the add screen of stock management and loose all the work the user has done

Design

• 
•  Mary Jo wants this table redesigned. We should discuss what it could look like Nick Reid (Deactivated).
•  Nick Reid (Deactivated), this is another table sort that we should update.
  
  

Performance

• REMOVE FONT-AWESOME
• Establish data budget
• Sonar to track application size - vendor libraries, html, translation strings, image sizes
• Sonar to track download time on 3g connection
• Sonar unit test coverage
• Sonar module dependency tracking
• 

Offline Support

• App Cache update detect and notification
• OfflineService component to simplify offline development
• Less frequent offline status check (reduce UI bandwidth)

Extensibility

Important before 3rd party starts working with codebase

Development Tools

• 
• Set up Javascript linter
• Set up Sass linter
• Dgeni-example JSDoc and KSS toolset
• Cordova Android application compiler

Malawi Features to Merge

src/openlmis-login/login.service.js - Would be cool to pull in clearUserData work, and make currency source configurable
src/openlmis-table/openlmis-table-container-shortner.directive.js - Needs unit tests but could be merged back in
src/openlmis-table/sticky-table-header.directive.js - Would be great to add this and sticky-table-footer back to core
src/openlmis-order-view/ - There has got to be a better way to structure these view files.... ideally the link logic could be changed or decorated

All changes in reports seem like great additions back to core

requisition-approval.controller.spec.js – doesn't actually fork the existing file, so it could remove any overlapping tests
I wonder if requisition approval functionality could have been implemented in a non-overlapping manner — its different enough that the code doesn't have any value in being forked...

requisition-search.html could be pulled back into core