jibees
July 19, 2022, 8:16am
1
Priority issues + code review
Works on matomo, and did a PR to move script at the good place.
Priority issues +
@maikel : Slack @maikel will delete the server and update the wiki. Only new instances with new language needs to open a PR when adding new langage.
jb: it’s positive. Happy to work with Maikel. it seems to be a good idea. Let’s continue on that way
Maikel: quite positive too. But completely focused on priority and so didn’t do to code review. Really enjoyed processing things quicker. More involved. Have to relax a little bit as well.
Next issues for the week:
opened 01:17PM - 26 Jun 19 UTC
bug-s4
Priority
## Description
If you upload an image on a product, or create a product with an… .svg image for example, the image won't be displayed. Only .png or .jpg are allowed, but the user does not know it.
## Steps to Reproduce
1. Go to `admin/products`
2. Create a product with a .svg image or edit a product image with a .svg file
3. See the display problem
## Animated Gif/Screenshot
## Severity
bug-s4: it's annoying, but you can use it
## Your Environment
* Version used: v2.1
* Browser name and version: Firefox 67
* Operating System and version (desktop or mobile): Ubuntu 19.10
opened 05:30PM - 09 Aug 21 UTC
UK
papercut
Priority
## Description
**- As an:** enterprise user
**- On page:** create backoffice o… rder
**- I want to be able to:** do this in a more straightforward way
We want to change the flow of the backoffice order creation process.
Currently it goes:
1. Order Details
2. Customer Details
3. Payments
4. Adjustments
The problem with this is that it demands the user switches back and forth between 1 and 2 a few times to fill in all the details.
We want to change to:
1. Customer Details
2. Order Details
3. Payments
4. Adjustments
So when 'New Order' is pressed in the backoffice the user should be taken to the 'Customer Details' screen first.
An order in state cart should be created at step 1.
It was noted that potential issues may arise if elements in 'Customer Details' step depend on 'Order Details' step. This should be solvable in half a day.
This change applies to the User Flow and also to the submenu. Please change the submenu accordingly.
## Acceptance Criteria & Tests
<!-- Document the outcomes that need to be achieved before this component can be considered complete.
-->
1. Test stopping at every point and that the order does not go into a corrupted state. State transitions should be well handled.
2. Test orders are created properly
3. This will probably benefit from some thorough testing of this flow with the distinct intention of trying to break it!
4. Product need to update the Order States miro board to reflect these changes
5. Product need to ensure hte User Guide is updated to reflect these changes
1 Like