...
...
Reason | Bug | Notes | Total | |
---|
UI refactors | |
(openlmis.atlassian.net)columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-3017 |
---|
|
| Caused by removing status messages from requisition object, but real cause why this was not working is Requisition Watcher which was setting $modified flag after requisition was submitted/authorized. This flag is a indicator if we have some changes in requisition object stored offline, if not application is getting new changes from server. Getting fresh changes after status change is crucial to have current comments on the screen. |
8JIRA (openlmis.atlassian.net) | columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-2837 |
Caused columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolutionSystem JIRA | serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-2837 |
---|
|
| Caused by refactor of facility/program select refactor. State param 'requestingFacilty' has been changed to 'facility' in order to be compatible with this new component. Unfortunately this parameter was used for search endpoint and this change caused lack of this parameter in request. | |
|
JIRA (openlmis.atlassian.net) | System JIRA | serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-2522 |
---|
|
| Caused by messages split refactor on the UI. | |
|
JIRA (openlmis.atlassian.net) | System JIRA | serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-2439 |
---|
|
| Caused by |
(openlmis.atlassian.net)columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
| serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-2050 |
---|
| . There are conflicting opinions on how this functionality should work, which makes it easy to overlook. It would be easy to assume that this is correct behavior after refactoring the pagination. | |
|
JIRA (openlmis.atlassian.net) | System JIRA | serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-2488 |
---|
|
| While working on |
(openlmis.atlassian.net) | serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-2050 |
---|
| the message keys were changed but usage of that keys was not changed. | |
|
(openlmis.atlassian.net)columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 448ba138-columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
| serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-2356 |
---|
|
| The whole list of columns was being passed to the validator instead of a list of the non full supply ones. | |
|
JIRA (openlmis.atlassian.net) | System JIRA | serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-2489 |
---|
|
| During message refactor message keys have changed but one of the if statement left unchanged, which caused to invalid values being returned. | |
|
(openlmis.atlassian.net)columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 448ba138 | serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-2352 |
---|
|
| During refactor of the template validator one of the validation wasn't implemented. | |
|
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution | serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-7217 |
---|
|
| Permissions were removed from local storage and retrieved from the backend again every time when the page was refreshed or logged user changed. It to was changed to not remove permissions when the page is refreshed. | |
|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-7220 |
In offline mode, facilities | serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-7220 |
---|
|
| In offline mode, facilities were not retrieved from the cache. As a solution, it was updated cachedAllMinimal to get facilities from PouchDb when offline. Additionally added refactor to getAll method in local database to reject when it is not available. | |
|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution | serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-7246 |
---|
| Jira Legacy |
---|
server | System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-7259 |
---|
|
| This page is using cache and the "openlmis-cached-resource" was removing the pagination information from the response when fetching stock data (in the "query" function). | |
|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-7271 |
---|
|
| Pagination fix done in |
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution | serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-7246 |
---|
| caused the the issue with displaying the Products. |
Other bug fixes (openlmis.atlassian.net)columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution | serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-5491 |
---|
|
| One time binding used for iterating over collection for column generation | |
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS- |
---|
|
|
2329Caused by lack of check if new value is different than the previous one while running calculations in product-grid directive for each digest cycle. It was changed while repairing lack of calculation calls for dependent columns commit | 17 | columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution | UI was assuming that processing period is required field, despite processing period is nullable on the backend | |
|
JIRA (openlmis.atlassian.net) | System JIRA | serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-7546 |
---|
|
| Plugin pouchdb-find was not in the project | |
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS- |
---|
|
|
2484During work on columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution | New order was created with null facility | |
|
JIRA (openlmis.atlassian.net) | System JIRA | serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-7464 |
---|
|
| There was no condition to check if the line item with 0 SoH is newly added. | |
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS- |
---|
|
|
1409, demo-data was added to Reference-Data but FTP settings in Fulfillment were not adjustedcolumns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
| Sometimes values in quantity column are changed when row is removed on Requisition-less order page. | |
|
JIRA (openlmis.atlassian.net) | System JIRA | serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS- |
---|
|
|
2466Validator was using calculatedOrderQuantity instead of the requestedQuantity. | The active flag was changed to ‘true’ for all products every time any product was added to inventory | |
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS- |
---|
|
|
7168Caused by gliderlabs/alpine image which is no longer maintained | Validation of inactive lots was not working on Physical Inventory page. | |
|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS- |
---|
|
|
7179Caused by renaming apache/incubator-superset to apache/superset | Error message for release without order with no requisitions selected was not defined. | |
|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS- |
---|
|
|
7203Caused by external Google Analytics dependency. | | Error message for with the description “Bad request Trade Item is required to add a Lot Code” was not defined. | |
Other bug fixes | |
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 448ba138-230b-serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS- |
---|
|
|
6856Demo-v3 has a local database on the instance. It was needed to create pgdata volume for deploy properly demo-v3 with KEEP option.
| Caused by lack of check if new value is different than the previous one while running calculations in product-grid directive for each digest cycle. It was changed while repairing lack of calculation calls for dependent columns commit | 32 | |
|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS- |
---|
|
|
6813There was a method that filtered out the products in which the | Caused by lack of check if recent stock on hand value was |
zero. For the Adjustments screen, a new method has been created that retrieves all available products in the facility - also those whose SoH is 0.0, the stockout days were calculated from the period between last physical inventory when SoH was zero instead of all entries when it was 0. In order go get previous period Map<K, V> datastructure was changed to NavigableMap<K, V> | |
|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolutionserverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-2484 |
---|
|
| During work on Jira Legacy |
---|
server | System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS- |
---|
|
|
7248Validation was added for programs in the orderable, but when creating new product program list is null and the validation threw NullPointerException, because null check was missing. | , demo-data was added to Reference-Data but FTP settings in Fulfillment were not adjusted.
| |
|
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution | serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS- |
---|
|
|
7253Facilities data source is no longer used since we started using Kafka. A new materialized view has been created - facilities that have all the necessary fields. | Jira Legacy |
---|
server | | Validator was using calculatedOrderQuantity instead of the requestedQuantity. | |
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS- |
---|
|
|
7254The data in the Stock Filter and District Stockout Rates over Time weren't visible. The time range setting for these charts has been changed to 'No filter' | Caused by gliderlabs/alpine image which is no longer maintained. | |
|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 448ba138-230b-serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS- |
---|
|
|
7291The current added products were not passed as a parameter to state params | Caused by renaming apache/incubator-superset to apache/superset | |
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS- |
---|
|
|
7398Expired nifi-registry certificate. Periodic ticket for certificate renewal was not created/finished on time. Certificate renewal automation should be considered | Caused by external Google Analytics dependency. | |
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-6856 |
---|
|
| Demo-v3 has a local database on the instance. It was needed to create pgdata volume for deploy properly demo-v3 with KEEP option. | |
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS- |
---|
|
|
7422Resolving supervisory nodes dataset required itself in injection | There was a method that filtered out the products in which the stock on hand was zero. For the Adjustments screen, a new method has been created that retrieves all available products in the facility - also those whose SoH is 0. | |
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-7248 |
---|
|
| Validation was added for programs in the orderable, but when creating new product program list is null and the validation threw NullPointerException, because null check was missing. | |
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-7253 |
---|
|
| Facilities data source is no longer used since we started using Kafka. A new materialized view has been created - facilities that have all the necessary fields. | |
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-7254 |
---|
|
| The data in the Stock Filter and District Stockout Rates over Time weren't visible. The time range setting for these charts has been changed to 'No filter'. | |
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-7291 |
---|
|
| The current added products were not passed as a parameter to state params | |
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-7398 |
---|
|
| Expired nifi-registry certificate. Periodic ticket for certificate renewal was not created/finished on time. Certificate renewal automation should be considered. | |
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-7422 |
---|
|
| Resolving supervisory nodes dataset required itself in injection | |
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-7420 |
---|
|
| Child state was not overwriting resolved children property from parent treating it as available via dedicated provider. Another form of issue from Jira Legacy |
---|
server | System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-7422 |
---|
|
| |
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-7437 |
---|
|
| Invalid docutils packge version was in use. | |
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-7429 |
---|
|
| There was no 'Label' specified for program_name column. | |
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-7442 |
---|
|
| For every dto transformation, request to referencedata was made. Timeout was caused by too many requests between stockmanagement abd referebcedata mikroservices | |
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-6646 |
---|
|
| Invalid search criteria specified in supserset | |
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-6546 |
---|
|
| Validation for unique product code was not implemented | |
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-6600 |
---|
|
| Class for representing certain status had invalid styling | |
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-7479 |
---|
|
| Feature to remember selection from other pages was not clearing selection after first convert | |
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-7496 |
---|
|
| Missing entries for proper roles in referencedata.role_rights table. Entries were missing also for demo data | |
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-7530 |
---|
|
| Endpoint /api/validSource s and /api/validDestinations are not returning all resources by default and list to search on when confirming shipment was to small | |
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-7499 |
---|
|
| When 'Remarks' is disabled in the requisition template, there is a null pointer exception when approving requisition. | |
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-7534 |
---|
|
| Validation on product code duplicate was not checking existing orderable properly | |
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-7527 |
---|
|
| active property was missing after creating difference between draft line items and display line items group
| |
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-7579 |
---|
|
| Validation on product quantity input was not checking empty/null values properly | |
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-7583 |
---|
|
| Regex in form decorator didn’t detect changes in reasonQuantity field in case of removing this field from form. | |
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-7581 |
---|
|
| There was the issue with sorting products. Now it works in such way that products are sorted by 'Original Index'. | |
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-7582 |
---|
|
| While investigation of this bug it realized that there was an issue when there was no draft created. Next page couldn’t be loaded when user chose program and click ‘start'. ‘PhysicalInventory’ form was displayed when user clicked again on ‘start’ button. This error didn’t happened when there was already created draft. The reason of this bug was an error with handling ‘null’ in ‘physical-inventory-factory.js’ within 'getStockAdjustments’ function. | |
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS- |
---|
|
|
7420Child state was not overwriting resolved children
property from parent treating it as available via dedicated provider. Another form of issue from This problem was related to 'losing states of Redux' after either refreshing or reloading application. | |
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
|
|
key | OLMIS-7422 | Unaccounted Quantity was not calculated when entering the draft, nor it was saved for items in draft. | |
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS- |
---|
|
|
7437Invalid docutils packge version was in use | Problem caused by cached some basic data related to permissions and list of programs/facilities. Now in “requisitions->create/authorize” those data are refreshed. | |
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS- |
---|
|
|
7429There was no 'Label' specified for program_name column | The ‘Search’ button on Initiate Report and Requisition page did not included the start date of a given program, but returned all found periods for a given facility and program. | | |
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS- |
---|
|
|
7442For every dto transformation, request to referencedata was made. Timeout was caused by too many requests between stockmanagement abd referebcedata mikroservices | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-6646 |
---|
|
| Invalid search criteria specified in supserset | Caused by a method that calculates stockout days. The method did not take into account the beginning balance of a given period and also incorrectly verified the occurrence of stock on hand in a given period. | | |
Design error | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-6008 |
---|
|
| There was neither unique constraint nor unique index on name in facility_types table | 18
| |
|
server | JIRA (openlmis.atlassian.net) |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolutioncolumns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
|
---|
server | System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-3146 |
---|
|
| There was no PROGRAM_MANAGE right at all, so it had to be added. | |
|
JIRA (openlmis.atlassian.net) | System JIRA | serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-3066 |
---|
|
| Caused by assumption that all modules that are using facility/program select component are using Requisition rights which is not true. | |
|
JIRA (openlmis.atlassian.net) | columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolutioncolumns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
| System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-3019 |
---|
|
| After authorize skipped line items are cleared and lack of price per pack field was causing the problem | |
|
JIRA (openlmis.atlassian.net) | System JIRA | serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-2714 |
---|
|
| Loading modal was closed too soon just after user update request finished, not after user list page was loaded. | |
|
server | JIRA (openlmis.atlassian.net) |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolutioncolumns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
|
---|
server | System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-2548 |
---|
|
| Loading spinner close method was always called before login modal appeared. Now there is a check if loading spinner was opened before opening loading modal, if so it will be reopened after successful login. | |
|
JIRA (openlmis.atlassian.net) | System JIRA | serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-2514 |
---|
|
| Check for approving requisition was including only program, supervisory node was missing. Fixed for approve and reject endpoint. | |
|
JIRA (openlmis.atlassian.net) | columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolutioncolumns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
| System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-2530 |
---|
|
| Requisition repository was returning page of filtered requisition, then right were checked and paginated once again, where total elements was number of requisitions on the page..... | |
|
JIRA (openlmis.atlassian.net) | System JIRA | serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-2428 |
---|
|
| We were using statusText property from server response, but it turned out that it was not always available. Lack of default message caused this issue. | |
|
server | JIRA (openlmis.atlassian.net) |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolutioncolumns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
|
---|
server | System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-2224 |
---|
|
| Offline flag at the start was always set as false at the start of offline service, so checking if user is offline just after reloading page/application always returned false. Resolved by storing offline flag in local storage. | |
|
JIRA (openlmis.atlassian.net) | System JIRA | serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-2481 |
---|
|
| Loading modal was closing after syncing was completed and then reopened when state changed(which happens after every requisition-related action). | |
|
JIRA (openlmis.atlassian.net) | columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolutioncolumns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
| System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-2483 |
---|
|
| Handling situation when there are no more products to add was never designed nor included in the acceptance criteria. | |
|
JIRA (openlmis.atlassian.net) | System JIRA | serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-2525 |
---|
|
| CalculationFactory was trying to calculate order quantity(rather than just taking the requestedQuantity) when requested quantity was |
empty. Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolutionempty. | |
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-2491 |
---|
|
| Subject and Content for notifications were part of demo-data. The system that didn't used demo-data was not able to go through Requisition statuses hierarchy because of absence settings in database. Settings were moved to Transifex messages and environment variables. | |
|
(openlmis.atlassian.net) | serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-2551 |
---|
|
| No thought was given to the transactional implications when the code was written. | |
|
(openlmis.atlassian.net)columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-2509 |
---|
|
| Incorrect calculation not taking borders into consideration which led to ever increasing table |
width. Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolutioncolumns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolutionwidth. | |
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-2532 |
---|
|
| During adding pagination to Manage POD view, clearing the requesting facility was not added when it was part of state params. | |
|
JIRA (openlmis.atlassian.net) | System JIRA | serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-2637 |
---|
|
| The password field was being cleared when we successfully logged in. | |
Questionable if this a bug | |
JIRA (openlmis.atlassian.net) | System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-2407 |
---|
|
| This is more a requirements change than a bug. |
3columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
JIRA (openlmis.atlassian.net) | System JIRA | serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-2453 |
---|
|
| This is more a requirements change than a bug. | |
|
server | JIRA (openlmis.atlassian.net) |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolutioncolumns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
server | System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-2480 |
---|
|
| This wasn't really a bug, more like an unrepresentative demo data. | |
|
JIRA (openlmis.atlassian.net) | System JIRA | serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-2492 |
---|
|
| There was no way to retrieve warehouses from server before. | |
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS- |
---|
|
|
2492There was no way to retrieve warehouses from server before | This is more a requirements change than a bug. | |
Not following style guide
| |
(openlmis.atlassian.net)columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-2445 |
---|
|
| UI style guide - programmers were not following styleguide sections: Titles and Buttons which say that first letter of each word should be capitalized. | 3 |
Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution | |
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-2471 |
---|
|
| Inline elements should have the same height. | |
|
(openlmis.atlassian.net)columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-2436 |
---|
|
| Inline elements should be aligned to center. | |
Invalid demo data |
Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-2531 |
---|
|
| Some of the requisitions that were in pre-release state had supplyingFacilityId set to a value that was not an UUID of one of the available supplying depot for that requisition |
.1 | . | 1 | |
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-7525 |
---|
|
| Some values of orderable identifiers were uppercase but expected to be lowercase | | |
Backend refactors | |
(openlmis.atlassian.net) | serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-3119 |
---|
|
| Caused by refactoring done to the Auth context setup in |
(openlmis.atlassian.net) | serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | MW-390 |
---|
| . | 6 | |
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-3461 |
---|
|
| Caused by refactor to do db filtering in Jira Legacy |
---|
server | System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-3187 |
---|
|
| |
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-7169 |
---|
|
| Caused by upgrading to Spring Boot 2.x Jira Legacy |
---|
server | System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-6782 |
---|
| . Since the upgrade, the Hikari connection wasn't closed and after it reached its limit (10 connections), the Jasper Reports were not generated. | |
|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-7219 |
---|
|
| Poor performance has been fixed by clearing Hibernate session after order and shipment created and setting Hibernate batch insert properties | |
|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution | serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-7251 |
---|
|
| When entity graph is used to fetch orderables with programs in one database query and the orderables are filtered by program code the list of related programs will also be filtered (not all programs will be returned for orderable). | |
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-7376 |
---|
|
| Caused by refactoring done to the Requisition Service in Jira Legacy |
---|
server | System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-5226 |
---|
| . | |