So if I read you properly @lin_d_hop you are starting to do some inception and share reflexion about the scope of this feature
So the need remains to enable producers to easily prepare the orders for the individual customers. For that you suggest that there should be multiple stories:
- the producer needs to see customer name in reports
- she needs to receive the customer details in the notify producer email ? (I would personally discuss that, I disagree, I think if we include all customers detail the “summary” email of what was ordered is going to be huge, I would rather redirect to the reports for customers detail, but I agree that we can at least review the template of the email)
- she needs to have the authorization from buyer to have access to his/her personal details. For me this should be included in the terms of sales and might not require a specific UI. We need to check, but anyway that is part of the scope I agree.
Anyway, the three points above for me will be discussed in the inception stage where we brainstorm about the things to be done and how we do them, if we do all in one iteration or multiple iterations, etc. So I think prioritizing this wishlist will cover discussing those points. So as there are 6 votes I think we are going to do the inception very soon, and if you want to drive that inception you will be most welcome to
About 3. As you say enable to identify customer on order view is a different story, even if as you say I see some connexion (linked to enable everyone to prepare orders, not only producers), I would rather prioritize two smaller features than try to pack them all in a big one that takes weeks and months to do… don’t you think ? If we prioritize 5 small things, then we can have another round of voting for next things earlier, that would be great !