Replies: 3 comments 2 replies
-
Remote Server (deprecated)No more issues will be added but here is the summary of outstanding ones. They'll be relocated to open-msupply repo and removed when time to implement (or move to workload) V1 Internal DocumentationThis includes database schema documentation via SchemaSpy, current API pattern, back end layers and directory structure, general architecture and potential "how to", and rust docs And all of these published to github pages via github hook (and then https://docs.msupply.foundation as suggested by @craigdrown)
V1 ImprovementsThis was carried over from refactor work. Included using map_err vs from trait in services,
Ungrouped V1 issues
Item and Name Details
Ungrouped IssuesIssues without an epic with lower priority, not likely in V1
Handle Donors in shipmentsQuery, assign for invoice and lines lines
Invoice CategoriesQuery and assign to invoice
Shipping MethodsQuery and assign to invoice
TransfersAlthough transfers are already implemented, some extra bits that need to be done (using change log for sync processing, outline backwards compatibility with non v5 sites) Users and PermissionsJust some carry over, as per issues:
Customer CreditsThis still needs full spec, can be done now I think with outbound shipments back to supplier Supplier ReturnsSimilar to Customer Credits Deployment ReadyI think only carry over is Installer (which has seperate issue in open-msupply repository Sync after V1 betaThere are extras to be added here, will be summed up in open-msupply repo issue, but in remote server repo. Need to sum this up in more details
Stocktake Remainder
Pricing AlignmentThis is somewhat important, we doing different things now in outbound and inbound, also final agreed solution is slightly different from both: https://github.com/openmsupply/remote-server/issues/947 Report
Requisitions RemainderAbility to create shipments from requisition lines (this is already mentioned in ungrouped v1) and refreshing soh and amc via api call, also mentioned in ungrouped issues https://github.com/openmsupply/remote-server/issues/811 (clarify that snapshot quantity is history) LoggingThis one is for logging server/user action but I think an overarching epic would be better to also combine #23 and needs to consider logging of events for debugging error state when we deploy Test ImageThis was for docker mainly, it's done in: https://github.com/openmsupply/omsupply-build-tools, it may need some updates if there is interest in using it (if there is then it should be relocated to open-msupply repo, otherwise removed). Other ungroupedDon't have an epic
Modified by & modified datetime Comes from a request to show last modified by and last modified in UI Derive report data query permissions Looks like for UI to show greyed out report (quick note, do they need to be greyed out ?) Postman collection Should be part of docs section Sync settings: test When initialising check settings and report back to UI (it's covered in other repo #66) Review design for item store relationship Some discussion about new way of doing item store relationship, I think it's resolved, but can keep as open issue
Extra login protection when user password has changed Although immediate issue was resolved, need to consider one tricky use case ~~Authentication Error upon logging Resolved |
Beta Was this translation helpful? Give feedback.
-
|
If it helps, moving issues from one repo to another should be fairly easy:
But still 1 by 1! Not sure if there is a bulk way... wonder if it could be done through github gql api... probably faster to do 1 by 1 but less interesting haha |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
Open mSupplyReport PDF PrintingI am not sure exactly what's outstanding apart from issues linked in remote server (see
Programs
There is also discussion about sync and merge (I think we are leaning towards simplicity, and potentially removing merging, hash, multiple parents and sacrificing by field change record as it's very rare scenario) #88 UngroupedThese are issues without epic. Would be good to discuss if we want to continue with epic labels from remote server (some of these are epics themselves) Number table rows requisitions Currently using response and request requisition (mSupply just has requisition I think and it's for both) Permissions via API Query for permissions, this also mentions more granular report permissions with linked remote server issue Report PDF Printing, but talks about redefining current resources Bootstrap mode open issues (Initialisation state, sync status, manual sync, started of as a carry over from initialisation/bootstrap mode, but a comment added listing F/E requirement for sync status, manual sync and possibly removing bootstrap mode (or possibly changing it). Sqlite build config on Android I think we have a temporary fix but need a more permanent fix for cache directory for sqlite to use Audit log Logging use activity, also it's mentioned in Sync Issues
There is also fractional number of packs, with discussions here https://github.com/openmsupply/org-issues/discussions/40 to me the summary of it is: much simpler to implement fractional number of packs (I think the main origin of it is placeholder line distribution, so this area should also be redistributed) Global constants file for front end constants like records per page Dependency update updating front end dependencies to latest version Electron client improvements Mark has done most of them there are some extras
Reinstate running restrictive cors in dev Reinstate flag to still run cors in dev and cors tests Diesel async Transition to use async everywhere, should accompany benchmark (or maybe start with benchmark) Remove sqlite enum constraints should be small, just remove Sqlite can panic while creating a new database and WAL on startup Sometimes sqlite panics creating new db and wall on startup
Compile error due to Autocomplete types Front end TS error for Autocomplete package ~~ Incorrect authentication error notification (f/e) ~~ Resolved, but still some discussions about persisting token bucket after server restart |
Beta Was this translation helpful? Give feedback.
-
Open mSupply Client (deprecated) |
Beta Was this translation helpful? Give feedback.
-
10/09/22
Wanted to have a good grasp of issues with overview over all of the issues and their status on a regular basis.
This requires regular effort of looking through all of the issues (or previous issues reports) and updating their status and perhaps overall progress, comments and direction.
Trying to replicate something that @mark-prins was doing here https://github.com/openmsupply/org-issues/discussions/39
And something that I've started before holiday
And weekly HSH progress report emails compiled by @jmbrunskill and @Chris-Petty
Not really sure what the format should be like, but I think we'll figure it, the main thing is consistent and regular effort toward this task.
EDIT: just realised there is also summary of issues or requirements in: https://github.com/openmsupply/open-msupply/issues
Beta Was this translation helpful? Give feedback.
All reactions