...
(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.Jira Legacy server JIRA (openlmis.atlassian.net) serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-2619
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.
(MUST)Jira Legacy server JIRA (openlmis.atlassian.net) Jira Legacy server JIRA (openlmis.atlassian.net) serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-2921
(MUST)Jira Legacy server JIRA (openlmis.atlassian.net) serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-2617
(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.Jira Legacy server JIRA (openlmis.atlassian.net) columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-29212915
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.Jira Legacy server JIRA (openlmis.atlassian.net) columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-2872 Jira Legacy server JIRA (openlmis.atlassian.net) serverId 448ba138columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-26172913
MUST)Jira Legacy server JIRA (
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.
(MUST)Jira Legacy server JIRA (openlmis.atlassian.net) columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-2915
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.Jira Legacy server JIRA (openlmis.atlassian.net) columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-2872
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.Jira Legacy server JIRA (openlmis.atlassian.net) columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-2913
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.Jira Legacy server JIRA (openlmis.atlassian.net) columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-2608
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.openlmis.atlassian.net) columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-2608
Connecting Stock Management and Requisitions (MUST)
(MUST)Jira Legacy server JIRA (openlmis.atlassian.net) serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-2833
(MUST)Jira Legacy server JIRA (openlmis.atlassian.net) serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-2694
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.
(MUST)Jira Legacy server JIRA (openlmis.atlassian.net) serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-2830
...