-
-
Notifications
You must be signed in to change notification settings - Fork 729
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Estimate work needed to allow producer to edit their products on hubs' orders #12893
Comments
Hi @RachL - Did a spike on this one, it's a 1±0.5 day effort for all the following tasks:
I have the following questions:
Thanks |
@chahmedejaz yes the hub has the ability here: So when working on the enterprise permissions, we should reuse that setting to check if producer are allowed or not. for the tab, I'm adding this to the agenda of tomorrow's product circle and let you know right away. |
Sure, thanks Rachel |
Delivery circle notes on this:
|
Thanks @mkllnk @chahmedejaz
What's the easiest? Note that in the case where we display all items, we should block the ability for the supplier to edit item they don't own.
I would leave them in first interation and we can see later if this is a problem. I can do the screenshot after check with product circle 👍 |
Thanks so much @mkllnk for the insights.
@RachL - I think showing all the items would be easiest, that way we just need to put checks on the action buttons along with some authorization checks. What do you think @mkllnk? |
FYI @tschumilas will double check with her users to understand if it is a problem that producers are seeing what shoppers have ordered from other producers. Once we have the info we can see how we progress with this. A couple of additional info that came out during our talk today:
|
David and I had differing opinions here. David thinks that it's easier to show all items and disable the ones you can't edit. In this case, you have the whole picture of the order and a displayed order total makes sense. I, on the other hand, thought that it would be easier to display only the items that can be edited. Then we don't need a version of the view with disabled items. And in case of many items, the supplier has the shortlist of the items they are controlling without distraction. Any order total needs to be hidden to not confuse. I reckon that we let @tschumilas decide on this one. Technically, it's not a big difference. |
So I've chatted with a group of producers. There are producers who don't want other suppliers in the same shop to see their prices, or to know how much product they are supplying to specific buyers. So, I think it would be best to display (on the order) only those items that can be edited (that is - only the items owned by the producer doing the editing). One question - about a producer ADDING items to an order. Will they sell all the OC products in the 'select a variant' drop down, |
Sorry for not getting back to you sooner, @tschumilas.
Got it, so in that case, as per Maikel's suggestion, we would hide all totals displaying on the order.
I strongly agree with this. We should only display the list of products that the producer owns, rather than all. Otherwise, it would be cumbersome for the producer. |
@RachL - After considering the additional details, it would take 2-3 days of effort to implement this feature. Thanks. |
Creating a proper issue here: #13031 Closing here |
Description
In order to handle openfoodfoundation/wishlist#172
- As a: producer without shops, but supplying other existing hubs
- On page:
/admin/orders
- I want to be able to do: see the orders containing my products in
admin/orders
and be able to edit them : add my products only, edit the quantity of my products only, delete my products only. Ideally the other products are hidden.Hubs need to have the ability to allow producers to do that.
⚠ if the hub does not allow the producer to do see customer names, customer names must be hidden here as well (we can hide the whole tab perhaps?)
Acceptance Criteria & Tests
The spike results need to give a clear solution in terms of tech solution. And an estimate of the amount of work needed. No development should be started at this stage.
The text was updated successfully, but these errors were encountered: