...
Time | Item | Who | Notes | ||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
10 min |
|
Josh's thoughts and questions:
| |||||||||||||||||||||
20 min |
|
| |||||||||||||||||||||
10 min |
|
| |||||||||||||||||||||
20 min | Open questions |
| |||||||||||||||||||||
5 min | New QA onboard |
|
Shiyu Jin (Deactivated), where are we with permissions? I'm pasting in what Lakshmi put together.
In the end I'd like something similar to requisitions to be completed for Stock Management so people can clearly see what is being built https://openlmis.atlassian.net/wiki/display/OP/Requisition+Rights.
Create | Update | Submit | Delete | View | |
Stock management _ create | X | X | X | ||
Stock management _ delete | X | ||||
Stock management _ view | X |
A few points of discussion:
- Which type of right are the above permissions? Requisitions is based off of program and facility. Admin are global rights. Please make sure to understand the different types so we are appropriately creating the stock management rights.
- I haven’t added anything around authorizations here – the PC discussion concluded we might eventually want the ability for someone to audit/confirm a periodic physical stock count, but that none of the other movements need approvals. Since we’ve tabled that for later, I suggest we look at what the rights structure for that story would be while researching the story.
- Ashraf had also mentioned sometimes large adjustments/stock movements needing extra information. I wonder if a “stock management_request info” right might be appropriate where the user has the right to send a message to the creator of the movement to provide additional information.
- I assume any rights around notifications will be handled by that Epic.
Action items
- Shiyu Jin (Deactivated), when making stories, please make sure to add the component "Stock Management". Also, let's make sure each story has a fix version indicating the desired release date. Thanks.